@sdetweil Thanks!
I copied the config.js.sample to config.js before running the downgrade commands.
After downgrading and rebooting, the Magic Mirror showed up on my Pi 0 with the default configuration.
@sdetweil Thanks!
I copied the config.js.sample to config.js before running the downgrade commands.
After downgrading and rebooting, the Magic Mirror showed up on my Pi 0 with the default configuration.
@sdetweil said in Installing on a Pi Zero:
sudo npm -i npm@6
I got an error. Thanks for helping out, this is a new build so I don’t mind if it gets messed up and I need to start over.
$ sudo npm -i npm@6
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/pi/package.json
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open ‘/home/pi/package.json’
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2021-08-03T22_48_17_691Z-debug.log
@sdetweil Thanks, error log emailed. Ive done this process before without error ~9 months ago. Maybe the rasbian version or magic mirror version has changed recently that is now causing the problem.
@sdetweil said in Installing on a Pi Zero:
pm2 logs --lines=100
This just the Magic Mirror base. I haven’t added any extra modules.
Unfortunately I cannot paste the pm2 logs output. When I try it gets caught in some sort of spam filter and won’t let me post.
@sdetweil , I went through a fresh SD card install for a Pi Zero W. raspbian and then the raspberry.sh script via your github page. I believe everything completed without error.
However when Magic Mirror launches on reboot, I get a blank page indicating:
This site can’t be reached
localhost refused to connect
Any idea what to do to troubleshoot?
Hi all, Please bare with me since I’m not totally understanding the pm2 service. I setup Magic Mirror on a Raspberry Pi0 with @sdetweil scripts. I can manually start Magic Mirror fine, but it does not start when I do a reboot of my pi. Any idea how to fix?
After reboot, I see this in pm2 status:
pi@mm1:~ $ pm2 status
┌─────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.12.0 │ fork │ N/A │ 0 │ 0 │ stopped │ 0% │ 0b │ pi │ enabled │
└─────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
When I check the pm2 log, I see:
2020-10-31T16:18:53: PM2 log: [PM2] This PM2 is not UP TO DATE
2020-10-31T16:18:53: PM2 log: [PM2] Upgrade to version 4.5.0
2020-10-31T19:29:27: PM2 log: App [MagicMirror:0] exited with code [134] via signal [SIGINT]
2020-10-31T19:29:27: PM2 log: App [MagicMirror:0] starting in -fork mode-
2020-10-31T19:29:27: PM2 log: App [MagicMirror:0] online
2020-10-31T19:30:01: PM2 log: Stopping app:MagicMirror id:0
2020-10-31T19:30:01: PM2 log: App [MagicMirror:0] exited with code [0] via signal [SIGINT]
2020-10-31T19:30:01: PM2 log: pid=9716 msg=process killed
2020-10-31T19:30:01: PM2 log: PM2 successfully stopped
2020-10-31T19:32:10: PM2 log: ===============================================================================
2020-10-31T19:32:10: PM2 log: --- New PM2 Daemon started ----------------------------------------------------
2020-10-31T19:32:10: PM2 log: Time : Sat Oct 31 2020 19:32:10 GMT-0400 (Eastern Daylight Time)
2020-10-31T19:32:10: PM2 log: PM2 version : 4.4.1
2020-10-31T19:32:10: PM2 log: Node.js version : 10.21.0
2020-10-31T19:32:10: PM2 log: Current arch : arm
2020-10-31T19:32:10: PM2 log: PM2 home : /home/pi/.pm2
2020-10-31T19:32:10: PM2 log: PM2 PID file : /home/pi/.pm2/pm2.pid
2020-10-31T19:32:10: PM2 log: RPC socket file : /home/pi/.pm2/rpc.sock
2020-10-31T19:32:10: PM2 log: BUS socket file : /home/pi/.pm2/pub.sock
2020-10-31T19:32:10: PM2 log: Application log path : /home/pi/.pm2/logs
2020-10-31T19:32:10: PM2 log: Worker Interval : 30000
2020-10-31T19:32:10: PM2 log: Process dump file : /home/pi/.pm2/dump.pm2
2020-10-31T19:32:10: PM2 log: Concurrent actions : 2
2020-10-31T19:32:10: PM2 log: SIGTERM timeout : 1600
2020-10-31T19:32:10: PM2 log: ===============================================================================
I can start Magic Mirror manually by issuing:
pi@mm1:~ $ pm2 restart MagicMirror
Use --update-env to update environment variables
[PM2] Applying action restartProcessId on app [MagicMirror](ids: 0)
[PM2] [MagicMirror](0) ✓
┌─────┬────────────────┬─────────────┬─────────┬─────────┬──────────┬────────┬──────┬───────────┬──────────┬──────────┬──────────┬──────────┐
│ id │ name │ namespace │ version │ mode │ pid │ uptime │ ↺ │ status │ cpu │ mem │ user │ watching │
├─────┼────────────────┼─────────────┼─────────┼─────────┼──────────┼────────┼──────┼───────────┼──────────┼──────────┼──────────┼──────────┤
│ 0 │ MagicMirror │ default │ 2.13.0 │ fork │ 792 │ 2s │ 0 │ online │ 0% │ 2.4mb │ pi │ enabled │
└─────┴────────────────┴─────────────┴─────────┴─────────┴──────────┴────────┴──────┴───────────┴──────────┴──────────┴──────────┴──────────┘
Thanks!
@sdetweil Thanks! It is much more clear now. My screen size truncated the “apply” parameter at the end of the line. Now that I scroll horizontally I see the “apply”. Thanks again for the feedback.
Thanks for the reply. I did read that but it just seemed a little confusing since it was the same bash command. I haven’t run the upgrade script yet, so it might be more clear when I do but i guess the script knows if it’s been run a 2nd time?
@sdetweil said in Installing on a Pi Zero:
@RushHour99 yes, note that u have to run two times.
Thanks! Out of curiosity, why do I need to run it 2 times? I would have missed that detail if you didn’t’ let me know.
@sdetweil said in Installing on a Pi Zero:
@sdetweil My Magic Mirror install on a Pi Zero has been running great. I see an alert now that there is a Magic Mirror Update available. Do I just run your upgrade-script.sh to bring my Pi Zero install up to date with Magic Mirror v2.13.0?