Open katjaq opened 2 years ago
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!
ok, if we update node but continue to use it in the same path (currently it is a .n installation), rerunning pm2 save
should not be required though.
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: