REM wont come online

[lockeandev]

I had to turn power off to my Intellicenter OCP and when it came back online I made the mistake of trying to have it set its time from the internet, I think that allowed it to update the firmware. so I rolled it back to 1.064 but I'm till having problems with REM. probably not related to the OCP firmware. Below is the output from pm2 monit logs for REM:

Any ideas on how to get REM back up and running?

[lockeandev]

I cleaned the npm cache and updates all the apps (REM, dashPanel, njsPC) and cleaned the npm cache. I no longer get an error, but REM still does not ever come online. not I just see the following repeat over and over:

[tagyoureit]

You have too many (5) dist/app.js commands running. Did you previously have PM2 running the apps? You can run pm2 ls to list or pm2 stop all to stop the processes.

[lockeandev]

Yes. PM2 was running fine for over two years. The power outage and un expected firmware upgrade to the intellicenter seems to have set off this most recent problem. 'pm2 ls' just shows the four expected apps. REM, njspc, dash panel, logrotate.

I can stop all and confirm they are stopped. And if I try to use npm start to start REM. I get the same error in the console....

[tagyoureit]

If you use pm2 monit (or pm2 logs rem) does it also show the same error? The only explanations I can think of is that two processes are trying to write to the file; the disk is full (you'd be seeing lots of problems), or maybe that individual file became write protected or the user running the process doesn't have the right permissions?

[lockeandev]

yes, pm2 logs show the same error. I tried setting the file permissions for the whole REM folder so that anyone has full permissions. No change. I tried another uninstall and reinstall. same thing REM works the first time, but if I pm2 stop all and pm2 start all, the next time it starts up, it throws the error. I have a 32 GB sd card, and 18 GB free.

[lockeandev]

Ok, so I think I figured it out. I think I had 2 gpio pins set to try to write out the same export? Not sure how that happened, but it must have been user error on my part. I restored my controller config from an older backup and it works fine now. I guess I must have mad a change and never rebooting the pi in 3 or 4 months. I just never noticed the error until I had a hard reboot due to a power outage this week.