pm2 doesnt work with crontab

sdetweil

i should have remembered the path problem

plainbroke

@sdetweil
Did the new MM and or trixie change the way crontab works? Mine has stopped working since the update to 2.33. I tried again tonight and will see if the changes work or not… also my mm.json file quit working. Hind sight is 20/20 should have left well enough alone…

sdetweil

@plainbroke I do not know

Sorry, I have to ask, you DID use a new sd card, right?

What does /var/log/syslog say about the crontab execution

Did you use crontab -e
Or sudo crontab -e

1st is run as user who executed the crontab command
2nd is run as root

plainbroke

@sdetweil
Using NVMe disk 256gb smallest I had on hand. 3 of them are exhibiting the same issues. I did try going back to Bookworm and I am still getthing a blank screen after a while. I ran npm run config:check it says all is good in the config.js ////
I am currently reloading from scratch.
Which OS is better for the 2.33 MM? 32 or 64 bit?
Wondering if I was using 32 bit and now the 64 bit is messing with me… So dang many things can mess with these little devices.

I only use crontab -e, should I try sudo crontab -e

sdetweil

@plainbroke no, without sudo is best

Maybe pm2 isn’t in the path when crontab fires
Check the syslog for crontab errors

32 bit is about to be trouble.

The latest nodejs version, 24, has dropped builds for 32 bit

plainbroke

@sdetweil
Thanks for the info I almost pulled down 32 bit.
It has been interesting to say the least going to trixie.
Turns out my problem was a failed NVMe drive.
I thought those things where supposed to last for a LONG long time…
I did get crontab -e to work with trixie and MM 2.33 not a fun ride, but entertaining. I finally learned how to use bash to make batch style files…
So not a complete loss of time…

sdetweil

@plainbroke technology is SOOOO much fun! Simple, til it’s not!

Thanks for the feedback. Others will ask, I’m sure they could use your help!

plainbroke

@sdetweil
Ok crontab -e worked last night to shutdown MM. So the pm2 stop all worked.
BUT this morning the pm2 restart mm did nothing.
I used find to get these:

/home/pi/MagicMirror/node_modules/.bin/pm2
/home/pi/MagicMirror/node_modules/pm2
/home/pi/MagicMirror/node_modules/pm2/bin/pm2
/home/pi/MagicMirror/node_modules/pm2/lib/templates/logrotate.d/pm2
/home/pi/MagicMirror/node_modules/pm2/pm2
/usr/local/bin/pm2
/usr/local/lib/node_modules/pm2
/usr/local/lib/node_modules/pm2/bin/pm2
/usr/local/lib/node_modules/pm2/lib/templates/logrotate.d/pm2
/usr/local/lib/node_modules/pm2/pm2

ANY idea on which one would work better.?
Here is my current crontab -e

# Turn off display at 9pm
00 21 * * 0-6 /usr/local/bin/pm2 stop all >/dev/null >2&1
# Turn on screen Monday - Friday at 6:45 am
45 06 * * 1-5 /usr/local/bin/pm2 start mm >/dev/null >2&1
# Turn on screen Saturday - Sunday at 7:30 am
30 07 * * 6,0 /usr/local/bin/pm2 start mm >/dev/null >2&1

sdetweil

@plainbroke which one, if any , are in the path
Are they all executable?

ls -laF
Will give you the permissions mask

Are any of them links to another?

What changed?

/usr/local/bin/pm2
Should be the one

sdetweil

@plainbroke also look in /var/log/syslog
To find the logging of the execute at the time it should fire