Not restarting after reboot

[smeddly]

I am sorry I am a VERY new user of Pi at all. I followed your instructions to do the easy install answered Yes at the end for the restart after reboot. At of the install you give a message something like " Easel Driver running in the back ground, run screen -r to bring it to the foreground" I need to do that before it works at that point it seems to work fine. Then if the Pi reboots the only way I can figure out to get it to work again is to do the install again.

[samyk]

Please output crontab -l and tail -100 ~/easel-driver/screenlog.0

[smeddly]

I’m not sure why it put the Strike-Through on some of the commands when I copied the text but they weren’t there when it was in the Terminal window.

@.***:~ $ crontab -l

@reboot . /.bashrc ; cd /easel-driver && /usr/bin/screen -L -dmS easel node iris.js

@reboot cd ~/easel-driver && /usr/bin/screen -dmS easel node iris.js

@.***: $ tail -100 /easel-driver/screenlog.0

2021-05-22T18:13:16.495Z iris.js [id=0] Starting Easel Driver 0.3.20

2021-05-22T18:13:16.506Z Machine [id=3] Resetting

2021-05-22T18:13:16.570Z iris.js [id=0] Listening on port 1438 for secure connections from easel.inventables.com:80 easel.inventables.com:443 easelstaging.inventables.com:80 easelstaging.inventables.com:443 easel.invinternal.com:443 easel-secure.inventables.com:443 easel-insecure.inventables.com:80

2021-05-22T18:13:16.585Z iris.js [id=0] Listening on port 1338 for connections from easel.inventables.com:80 easel.inventables.com:443 easelstaging.inventables.com:80 easelstaging.inventables.com:443 easel.invinternal.com:443 easel-secure.inventables.com:443 easel-insecure.inventables.com:80

2021-05-22T18:13:17.138Z Websocket Controller [id=4] Client connected via polling

2021-05-22T18:13:18.600Z Websocket Controller [id=4] Client transport changed to websocket

2021-05-22T18:13:39.583Z Machine [id=3] Setting config: GRBL 0.9 Default Configs

2021-05-22T18:13:39.589Z Machine [id=3] Resetting

2021-05-22T18:13:39.596Z Machine [id=3] Opening port: /dev/ttyUSB0

2021-05-22T18:13:39.803Z Serial port controller [id=2] Port opened

2021-05-22T18:14:13.184Z Machine [id=3] Client disconnected (0 remaining)

2021-05-22T18:14:23.187Z Machine [id=3] Resetting

Cannot exec 'node': No such file or directory

@.***:~ $

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Samy @.> Sent: Saturday, May 22, 2021 12:20 PM To: @.> Cc: @.>; @.> Subject: Re: [samyk/easel-driver] Not restarting after reboot (#16)

Please output crontab -l and tail -100 ~/easel-driver/screenlog.0

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/samyk/easel-driver/issues/16#issuecomment-846452316, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAK5PWPW75T2WKJC7AMIRETTO77WXANCNFSM45K43EDQ.

[acavella]

Not a huge fan of the @reboot cron service and find it unreliable.

I'd like to create a pull request to add an actual init.d / systemd service to the install. Would this be a change you'd be interested in merging?

[samyk]

Sure

On Sun, Aug 1, 2021 at 4:53 AM Tony Cavella @.***> wrote:

Not a huge fan of the @reboot https://github.com/reboot cron service and find it unreliable.

I'd like to create a pull request to add an actual init.d / systemd service to the install. Would this be a change you'd be interested in merging?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/samyk/easel-driver/issues/16#issuecomment-890505658, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADEROEAARWLUXYOXU3F2CTT2UYTBANCNFSM45K43EDQ .

-- @SamyKamkar https://twitter.com/samykamkar https://samy.pl