You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem was due to pm2 save done on the previous node version, so it was trying to run on it after a system reboot. If we want to rely on pm2 save to be able to automatically start brainbox at system boot, I don’t think there is another way than rerunning pm2 save after having changed the location of node. Another solution would be to instead use a custom startup script to do the job.
Thank you ! Both sounds good to me. For now , it worked fine just to install the new node and restart using the updated environment. But by the time we change to the next updated node we will need to remember to run those steps again if we don't make the custom startup script... 😇
Thanks!
For some reason, BrainBox restarted and went back to using the wrong version of node. This causes a complete crash of BrainBox (service unavailable).
Can we make sure that in case of restart BrainBox automatically uses the correct version of node? @ntraut @dhovart
error log:
The text was updated successfully, but these errors were encountered: