• SoftwareIDE

  • Bela IDE refused to connect even though ssh can work

use journalctl -fu bela_ide -n 300, it shows
Nov 03 17:16:54 bela systemd[1]: Started Bela IDE Launcher.
Nov 03 17:17:00 bela systemd[1]: bela_ide.service: Main process exited, code=killed, status=11/SEGV
Nov 03 17:17:00 bela systemd[1]: bela_ide.service: Unit entered failed state.
Nov 03 17:17:00 bela systemd[1]: bela_ide.service: Failed with result 'signal'.
Nov 03 17:17:01 bela systemd[1]: bela_ide.service: Service hold-off time over, scheduling restart.
Nov 03 17:17:01 bela systemd[1]: Stopped Bela IDE Launcher.
Nov 03 17:17:01 bela systemd[1]: Started Bela IDE Launcher.
Nov 03 17:17:02 bela systemd[1]: bela_ide.service: Main process exited, code=killed, status=11/SEGV
Nov 03 17:17:02 bela systemd[1]: bela_ide.service: Unit entered failed state.
Nov 03 17:17:02 bela systemd[1]: bela_ide.service: Failed with result 'signal'.
Nov 03 17:17:03 bela systemd[1]: bela_ide.service: Service hold-off time over, scheduling restart.
Nov 03 17:17:03 bela systemd[1]: Stopped Bela IDE Launcher.
Nov 03 17:17:03 bela systemd[1]: Started Bela IDE Launcher.

I am always amazed when node gives a segmentation fault ... Once you sshed on the board, can you run the following:

systemctl stop bela_ide
cd /root/Bela/IDE
node index.js

what do you get as an output from the last command?

    giuliomoro Thanks. When I manually run the node, it works. The last line is "listening on port 80".
    Then I can connect to the IDE.

      hmm I cannot fathom why it would fail when running at boot then ...

      Try this please:

      • Reboot
      • wait a minute
      • ssh on to the board
      • run journalctl -u bela_ide -n 3000 | cat : do the first few lines (not included in your previous message), or any other lines show any more meaningful messages than the above?
      • run systemctl start bela_ide
        and then see what journalctl -fu bela_ide has to say: does it run now or fail again?

        giuliomoro journalctl -u bela_ide -n 3000 | cat

        root@bela:~# journalctl -u bela_ide -n 3000 | cat
        -- Logs begin at Thu 2016-11-03 17:16:43 UTC, end at Thu 2016-11-03 17:19:26 UTC. --
        Nov 03 17:16:53 bela systemd[1]: Started Bela IDE Launcher.
        Nov 03 17:17:00 bela systemd[1]: bela_ide.service: Main process exited, code=killed, status=11/SEGV
        Nov 03 17:17:00 bela systemd[1]: bela_ide.service: Unit entered failed state.
        Nov 03 17:17:00 bela systemd[1]: bela_ide.service: Failed with result 'signal'.
        Nov 03 17:17:01 bela systemd[1]: bela_ide.service: Service hold-off time over, scheduling restart.
        Nov 03 17:17:01 bela systemd[1]: Stopped Bela IDE Launcher.

          giuliomoro journalctl -fu bela_ide

          root@bela:~# journalctl -fu bela_ide
          -- Logs begin at Thu 2016-11-03 17:16:43 UTC. --
          Nov 03 17:20:46 bela systemd[1]: bela_ide.service: Failed with result 'signal'.
          Nov 03 17:20:47 bela systemd[1]: bela_ide.service: Service hold-off time over, scheduling restart.
          Nov 03 17:20:47 bela systemd[1]: Stopped Bela IDE Launcher.

            giuliomoro
            node index.js also works at times. It may cause the segmental error. really strange

              Hmmm sounds like maybe a corrupted file somewhere? Can you try reflashing the image?