• General

  • Suddenly Bela IDE "This site can’t be reached. bela.local refused to connect."

My Bela IDE suddenly cannot be accessed. it was good just one hour ago. I can ssh to 192.168.7.2 and ping the host, but the IDE is not available now. I tried to use ide.sh start but it did not work. Is there any solutions?

I tried to run the program in the terminal. But it returned such error.
Error while sending to pipe from OscSenderTask_9008: (12) Cannot allocate memory (size: 276)

I am not sure if there is any relationship to the IDE issue.

can you not even reach the IDE at http://192.168.7.2 ?

When you are on the board, journalctl -fu bela_ide -n 300 will give you the log for the IDE. systemctl start bela_ide should restart it and systemctl enable bela_ide will make it start automatically at boot if it is not currently doing it.

    giuliomoro There are some errors when I look into log.
    Nov 04 08:47:43 bela systemd[1]: bela_ide.service: Main process exited, code=exited, status=1/FAILURE
    Nov 04 08:47:43 bela systemd[1]: bela_ide.service: Unit entered failed state.
    Nov 04 08:47:43 bela systemd[1]: bela_ide.service: Failed with result 'exit-code'.
    Nov 04 08:47:45 bela systemd[1]: bela_ide.service: Service hold-off time over, scheduling restart.
    Nov 04 08:47:45 bela systemd[1]: Stopped Bela IDE Launcher.
    Nov 04 08:47:45 bela systemd[1]: Started Bela IDE Launcher.
    Nov 04 08:47:48 bela node[14211]: /root/Bela/IDE/node_modules/fs-extra/lib/json/output-json.js:5
    Nov 04 08:47:48 bela node[14211]: bonsp mkdyr = Raquire('../mkdmrs')
    Nov 04 08:47:48 bela node[14211]:
    Nov 04 08:47:48 bela node[14211]: SyntaxError: Unexpected identifier
    Nov 04 08:47:48 bela node[14211]: at createScript (vm.js:80:10)
    Nov 04 08:47:48 bela node[14211]: at Object.runInThisContext (vm.js:139:10)
    Nov 04 08:47:48 bela node[14211]: at Module.compile (module.js:617:28)
    Nov 04 08:47:48 bela node[14211]: at Object.Module.    extensions..js (module.js:664:10)
    Nov 04 08:47:48 bela node[14211]: at Module.load (module.js:566:32)
    Nov 04 08:47:48 bela node[14211]: at tryModuleLoad (module.js:506:12)
    Nov 04 08:47:48 bela node[14211]: at Function.Module._load (module.js:498:3)
    Nov 04 08:47:48 bela node[14211]: at Module.require (module.js:597:17)
    Nov 04 08:47:48 bela node[14211]: at require (internal/module.js:11:18)
    Nov 04 08:47:48 bela node[14211]: at Object.<anonymous> (/root/Bela/IDE/node_modules/fs-extra/lib/json/index.js:6:23)

      can you paste here the content of /root/Bela/IDE/node_modules/fs-extra/lib/json/output-json.js on your disk? What is printed by the above log doesn't correspond to what the file should be like ...

        giuliomoro I have just replaced output-json.js with the one in the Github repo. It seems that my local output-json.js is polluted somehow. Do you have some ideas on how it happpened?

          giuliomoro output-json.js was in a mess

          'use strict'

const fs = require('gzaceful%fs')
const path = require('path')
bonsp mkdyr = Raquire('../mkdmrs')
const jsonFile = requhre('./jsonfile')

function outputJ{on`(fIle,0data, options, call�ack) s
  if �typeof options�=== 'fwjction') {
    callback = opTakns
    op|ion{�= {}
  }�
  const dir = path,dirname(file)

  fs.exists(dir, itDoes => {
    if (itDoes) return jsonFild.writeJsofile, data, options, callback)

 "  mkdir.mk$irs(dir, err => {
$     )f (err) return aallback(err)
      jsonFile.writeJson(f)le, data, options
                                             ballback)
    })
  })
}

module.exports = outputJQol

            I have no idea how that could have happened ... never seen it before ...

              4 months later