Blank mm after update

[evroom]

@kvicksson said in Blank mm after update:

@sdetweil Thanks! This worked for me

I should type faster :-)

[sdetweil]

@evroom think u have good instructions…

ps, 2 of my three systems do not have pi as the user, so the path is wrong, and in the module defaults too

[evroom]

@sdetweil said in Blank mm after update:

2 of my three systems do not have pi as the user

Yes, I assumed user pi and the install under the user pi home directory.
Will try to remember that in the future.
Tilde for the home directory should work on all platforms, is my understanding.

~/MagicMirror

My keyboard is lacking a tilde and I always forget the right keystrokes.
So /home/pi is faster. :-)

[kvicksson]

@evroom I sat right now and installed a new calendar module and suddenly the mmm-weatherchart started working… :thinking_face:

Did the $ pm2 logs --lines 100 and got a lot of errors, but I guess because everything’s working fine so don’t have to bother right now?!

[kvicksson]

And of course it didn’t work now when I tried to switch back to default calendar module and then back to the other calendar module…

[evroom]

@kvicksson said in Blank mm after update:

so don’t have to bother right now?

As long as the errors are no fatal errors that do not prevent the MagicMirror from starting or prevent a certain module from working right, you might chose to ignore them.
But the problem is, that when you add something new or update something existing, it becomes more and more difficult to debug and/or correct in case of problems.

When you do this:

$ pm2 flush
$ pm2 restart mm
$ pm2 logs --lines 100

what is the first error you see ?
Perhaps you post the first 50 to 100 lines of the log.

But only if you want to spend some time on it, when not that’s fine too.

[kvicksson]

@evroom actually no errors like I got before…

PM2        | 2019-08-29T21:46:00: PM2 log: pid=1331 msg=failed to kill - retrying in 100ms
PM2        | 2019-08-29T21:46:00: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2        | 2019-08-29T21:46:00: PM2 log: pid=1331 msg=process killed
PM2        | 2019-08-29T21:46:00: PM2 log: App [mm:0] starting in -fork mode-
PM2        | 2019-08-29T21:46:00: PM2 log: App [mm:0] online

/home/pi/.pm2/logs/mm-out.log last 100 lines:
0|mm       | Shutting down server...
0|mm       | Stopping module helper: updatenotification
0|mm       | Stopping module helper: mmm-systemtemperature
0|mm       |
0|mm       | > magicmirror@2.8.0 start /home/pi/MagicMirror
0|mm       | > sh run-start.sh
0|mm       |
0|mm       | Starting MagicMirror: v2.8.0
0|mm       | Loading config ...
0|mm       | Loading module helpers ...
0|mm       | No helper found for module: alert.
0|mm       | Initializing new module helper ...
0|mm       | Module helper loaded: updatenotification
0|mm       | Initializing new module helper ...
0|mm       | Module helper loaded: mmm-systemtemperature
0|mm       | No helper found for module: clock.
0|mm       | Initializing new module helper ...
0|mm       | Module helper loaded: calendar
0|mm       | Initializing new module helper ...
0|mm       | Module helper loaded: MMM-YrThen
0|mm       | Initializing new module helper ...
0|mm       | Module helper loaded: mmm-weatherchart
0|mm       | Initializing new module helper ...
0|mm       | Module helper loaded: newsfeed
0|mm       | All module helpers loaded.
0|mm       | Starting server on port 8080 ...
0|mm       | Server started ...
0|mm       | Connecting socket for: updatenotification
0|mm       | Connecting socket for: mmm-systemtemperature
0|mm       | Starting node helper: mmm-systemtemperature
0|mm       | Connecting socket for: calendar
0|mm       | Starting node helper for: calendar
0|mm       | Connecting socket for: MMM-YrThen
0|mm       | MMM-YrThen 8/29/2019 9:46:08 PM: Starting helper for MMM-YrThen
0|mm       | Connecting socket for: mmm-weatherchart
0|mm       | Starting node helper: mmm-weatherchart
0|mm       | Connecting socket for: newsfeed
0|mm       | Starting module: newsfeed
0|mm       | Sockets connected & modules started ...
0|mm       | Launching application.

/home/pi/.pm2/logs/mm-error.log last 100 lines:
0|mm       | /home/pi/MagicMirror/node_modules/electron/dist/electron: /lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /home/pi/MagicMirror/node_modules/electron/dist/electron)
0|mm       | /home/pi/MagicMirror/node_modules/electron/dist/electron: /lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /home/pi/MagicMirror/node_modules/electron/dist/electron)
0|mm       | (node:2465) [DEP0025] DeprecationWarning: sys is deprecated. Use util instead.
0|mm       | /proc/self/exe: /lib/arm-linux-gnueabihf/libdbus-1.so.3: no version information available (required by /proc/self/exe)
0|mm       | ATTENTION: default value of option force_s3tc_enable overridden by environment.

I really appreciate you want to look into my errors, I’m not too good on this :)

[evroom]

@kvicksson

Doesn’t look too bad.
Probably you saw the previous errors in your log output, that it is why flushing (pm2 flush) sometimes cannot hurt.

In order to know a bit about your environment, can you post the output of the following commands ?
I am assuming you are using a Raspberry Pi

$ cat /proc/device-tree/model
$ lsb_release -a
$ npm --version
$ node --version
$ pm2 --version
$ cat /boot/config.txt | egrep -v '^$|^#|^\['

I also would suggest to see if npm shows any errors:

$ cd ~/MagicMirror
$ npm audit

In my case a

$ npm audit fix

solved the dependency issues it found.

Perhaps others have different ideas, but as a hobbyist, I would take these steps first myself.

[lavolp3]

@evroom said in Blank mm after update:

In my case a
$ npm audit fix

solved the dependency issues it found.

The npm audit warnings do not create any problems in running the mirror as far as I know. They also do not show up in the pm2 logs.
I would even be very careful as an inexperienced user to do that. “Fixing” these npm warnings on the root MM install could break the whole mirror (not the mirror itself of course :-)). Especially if you mess with the electron/chromium dependencies.

[kvicksson]

@evroom got an error on the egrep command:

pi@raspberrypi:~ $ cat /proc/device-tree/model
Raspberry Pi 3 Model B Rev 1.2pi@raspberrypi:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description:    Raspbian GNU/Linux 8.0 (jessie)
Release:        8.0
Codename:       jessie
pi@raspberrypi:~ $ npm --version
5.6.0
pi@raspberrypi:~ $ node --version
v9.11.2
pi@raspberrypi:~ $ pm2 --version
3.5.1
pi@raspberrypi:~ $ cat /boot/config.txt | egrep -v '^$|^#|^['
grep: Invalid regular expression