@sdetweil Wait! - I think I got it!

Thank you!

@sdetweil not that I know of.

pm2 show mm says the script path is /home/pi/mm.sh;
/home/pi/mm.sh did not have the GPU command in it.
I did change the one in ~/MagicMirror/installers, but since that doesn’t seem to be the right one,
I changed the one in /home/pi and pm2 restart mm - and now we have zero errors in the pm2 log.

One down.

However…MMM-RAIN-MAP still shows diddly-squat. And it’s still not showing in the right place.
npm config check comes back without errors. By the way, I thought I posted the question in the MMM-RAIN-MAP forum, but perhaps an error on my part.

@sdetweil Not sure if the last response took or not. GPU edit to mm.sh is complete, I did a hard boot afterwards. Response to uname command:

Linux MagicMirror 5.10.103-v7l+ #1529 SMP Tue Mar 8 12:24:00 GMT 2022 armv7l GNU/Linux

added the GPU setting to mm.sh; this is a Pi 3, ARMv71.

Errors in the console tab indicate

Uncaught (in promise) Error: Attempted to load an infinite number of tiles
at i._update (MMM-RAIN-MAP.js:28:109437)
at i._setView (MMM-RAIN-MAP.js:28:107836)
at i._resetView (MMM-RAIN-MAP.js:28:107173)
at i.onAdd (MMM-RAIN-MAP.js:28:102869)
at i._layerAdd (MMM-RAIN-MAP.js:28:64792)
at i.whenReady (MMM-RAIN-MAP.js:28:42729)
at i.addLayer (MMM-RAIN-MAP.js:28:65167)
at Class. (MMM-RAIN-MAP.js:28:149754)
at Generator.next ()
at a (MMM-RAIN-MAP.js:28:169)

No idea if this and the other error problem are related.

That didn’t seem to do it. After a pm2 flush, it shows

/home/pi/.pm2/logs/mm-error.log last 50 lines:
0|mm | [1176:0208/151743.603505:ERROR:connection.cc(46)] X connection error received.
0|mm | Gdk-Message: 15:17:43.634: electron: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
0|mm |
0|mm | [08.02.2023 15:18.16.665] [WARN] You’re using a full whitelist configuration to allow for all IPs
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load driver: kms_swrast
0|mm | MESA-LOADER: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load swrast driver
0|mm | [998:0208/151919.102171:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
0|mm | [998:0208/151919.105457:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!

I get a blank map as well.

pm2 logs:
pm2 log --lines=50
[TAILING] Tailing last 50 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 50 lines:
PM2 | 2023-02-08T12:57:12: PM2 log: App [mm:0] exited with code [1] via signal [SIGINT]
PM2 | 2023-02-08T12:57:12: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2023-02-08T12:57:12: PM2 log: App [mm:0] online
PM2 | 2023-02-08T12:57:15: PM2 log: Stopping app:mm id:0
PM2 | 2023-02-08T12:57:15: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2023-02-08T12:57:15: PM2 log: pid=1449 msg=process killed
PM2 | 2023-02-08T12:57:15: PM2 log: PM2 successfully stopped
PM2 | 2023-02-08T12:57:38: PM2 log: ===============================================================================
PM2 | 2023-02-08T12:57:38: PM2 log: — New PM2 Daemon started ----------------------------------------------------
PM2 | 2023-02-08T12:57:38: PM2 log: Time : Wed Feb 08 2023 12:57:38 GMT-0500 (Eastern Standard Time)
PM2 | 2023-02-08T12:57:38: PM2 log: PM2 version : 4.4.1
PM2 | 2023-02-08T12:57:38: PM2 log: Node.js version : 19.6.0
PM2 | 2023-02-08T12:57:38: PM2 log: Current arch : arm
PM2 | 2023-02-08T12:57:38: PM2 log: PM2 home : /home/pi/.pm2
PM2 | 2023-02-08T12:57:38: PM2 log: PM2 PID file : /home/pi/.pm2/pm2.pid
PM2 | 2023-02-08T12:57:38: PM2 log: RPC socket file : /home/pi/.pm2/rpc.sock
PM2 | 2023-02-08T12:57:38: PM2 log: BUS socket file : /home/pi/.pm2/pub.sock
PM2 | 2023-02-08T12:57:38: PM2 log: Application log path : /home/pi/.pm2/logs
PM2 | 2023-02-08T12:57:38: PM2 log: Worker Interval : 30000
PM2 | 2023-02-08T12:57:38: PM2 log: Process dump file : /home/pi/.pm2/dump.pm2
PM2 | 2023-02-08T12:57:38: PM2 log: Concurrent actions : 2
PM2 | 2023-02-08T12:57:38: PM2 log: SIGTERM timeout : 1600
PM2 | 2023-02-08T12:57:38: PM2 log: ===============================================================================
PM2 | 2023-02-08T12:57:38: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2023-02-08T12:57:39: PM2 log: App [mm:0] online

/home/pi/.pm2/logs/mm-error.log last 50 lines:
0|mm | Gdk-Message: 12:57:12.315: electron: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
0|mm |
0|mm | [08.02.2023 12:57.47.691] [WARN] You’re using a full whitelist configuration to allow for all IPs
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load driver: kms_swrast
0|mm | MESA-LOADER: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load swrast driver

/home/pi/.pm2/logs/mm-out.log last 50 lines:
0|mm |
0|mm | > magicmirror@2.22.0 start
0|mm | > DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js
0|mm |
0|mm |
0|mm | > magicmirror@2.22.0 start
0|mm | > DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js
0|mm |
0|mm | [08.02.2023 12:57.46.868] [LOG] Starting MagicMirror: v2.22.0
0|mm | [08.02.2023 12:57.46.881] [LOG] Loading config …
0|mm | [08.02.2023 12:57.46.890] [LOG] Loading module helpers …
0|mm | [08.02.2023 12:57.46.893] [LOG] No helper found for module: MMM-pages.
0|mm | [08.02.2023 12:57.46.895] [LOG] No helper found for module: alert.
0|mm | [08.02.2023 12:57.46.925] [LOG] Initializing new module helper …
0|mm | [08.02.2023 12:57.46.926] [LOG] Module helper loaded: updatenotification
0|mm | [08.02.2023 12:57.46.931] [LOG] No helper found for module: clock.
0|mm | [08.02.2023 12:57.47.391] [LOG] Initializing new module helper …
0|mm | [08.02.2023 12:57.47.392] [LOG] Module helper loaded: calendar
0|mm | [08.02.2023 12:57.47.394] [LOG] No helper found for module: MMM-OpenmapWeather.
0|mm | [08.02.2023 12:57.47.397] [LOG] No helper found for module: weather.
0|mm | [08.02.2023 12:57.47.398] [LOG] No helper found for module: compliments.
0|mm | [08.02.2023 12:57.47.456] [LOG] Initializing new module helper …
0|mm | [08.02.2023 12:57.47.456] [LOG] Module helper loaded: newsfeed
0|mm | [08.02.2023 12:57.47.461] [LOG] Initializing new module helper …
0|mm | [08.02.2023 12:57.47.461] [LOG] Module helper loaded: MMM-GoogleMapsTraffic
0|mm | [08.02.2023 12:57.47.463] [LOG] No helper found for module: MMM-RAIN-MAP.
0|mm | [08.02.2023 12:57.47.463] [LOG] All module helpers loaded.
0|mm | [08.02.2023 12:57.47.679] [LOG] Starting server on port 8080 …
0|mm | [08.02.2023 12:57.47.705] [LOG] Server started …
0|mm | [08.02.2023 12:57.47.706] [LOG] Connecting socket for: updatenotification
0|mm | [08.02.2023 12:57.47.707] [LOG] Starting module helper: updatenotification
0|mm | [08.02.2023 12:57.47.707] [LOG] Connecting socket for: calendar
0|mm | [08.02.2023 12:57.47.708] [LOG] Starting node helper for: calendar
0|mm | [08.02.2023 12:57.47.709] [LOG] Connecting socket for: newsfeed
0|mm | [08.02.2023 12:57.47.710] [LOG] Starting node helper for: newsfeed
0|mm | [08.02.2023 12:57.47.710] [LOG] Connecting socket for: MMM-GoogleMapsTraffic
0|mm | [08.02.2023 12:57.47.711] [LOG] Starting node_helper for module: MMM-GoogleMapsTraffic
0|mm | [08.02.2023 12:57.47.711] [LOG] Sockets connected & modules started …
0|mm | [08.02.2023 12:57.49.275] [LOG] Launching application.
0|mm | [08.02.2023 12:58.09.434] [LOG] Create new calendarfetcher for url: https://calendar.google.com/calendar/ical/k39nipendaanqj8de8v64pe69c%40group.calendar.google.com/public/basic.ics - Interval: 300000
0|mm | [08.02.2023 12:58.09.507] [LOG] Create new calendarfetcher for url: https://hcpss.instructure.com/feeds/calendars/user_RYJRLgcn84NLeddwOXFvYDYlx1disrEI08vTxnfn.ics - Interval: 300000
0|mm | [08.02.2023 12:58.09.518] [LOG] Create new newsfetcher for url: http://www.nytimes.com/services/xml/rss/nyt/HomePage.xml - Interval: 300000
0|mm | [08.02.2023 12:58.09.528] [LOG] Working notification system. Notification: MMM-GOOGLE_MAPS_TRAFFIC-GET payload: { style: ‘standard’ }
0|mm | [08.02.2023 12:58.09.566] [LOG] Create new calendarfetcher for url: https://hcpss.instructure.com/feeds/calendars/user_RYJRLgcn84NLeddwOXFvYDYlx1disrEI08vTxnfn.ics - Interval: 300000
0|mm | [08.02.2023 12:58.10.331] [INFO] Newsfeed-Fetcher: Broadcasting 24 items.
0|mm | [08.02.2023 12:58.11.436] [INFO] Calendar-Fetcher: Broadcasting 54 events.
0|mm | [08.02.2023 12:58.11.699] [INFO] Calendar-Fetcher: Broadcasting 65 events.
0|mm | [08.02.2023 12:58.11.886] [INFO] Calendar-Fetcher: Broadcasting 70 events.

And my config.js file:
module: “MMM-RAIN-MAP”,
position: “bottom_center”,
header: ‘Local Radar’,
config: {
// mapPositions: [{lat: 39.2331257, lng: -76.9903423}],
mapPositions: [{lat: 39.233, lng: -76.990}],
// mapHeight: “700px”, //optional default
// mapWidth: “700px”, //optional default
} // end config

And it’s ignoring the bottom_center positioning, too. I have MMM-pages running; perhaps I’ll see if that needs updating as well. Any suggestions?

updated to node 19.6.0

Still having the following error:

/home/pi/.pm2/logs/mm-error.log last 50 lines:
0|mm | Gdk-Message: 12:52:54.219: electron: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
0|mm |
0|mm | [08.02.2023 12:53.25.900] [WARN] You’re using a full whitelist configuration to allow for all IPs
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load driver: kms_swrast
0|mm | MESA-LOADER: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load swrast driver

I then did a sudo apt-get update then a sudo apt-get upgrade; it upgraded a couple of xserver files. Cleared the PM2 log and rebooted. Same errors as above.

Using a Pi - just did a full-upgrade, and then an git pull && npm install --only=prod --omit=dev

MM starts - but there are display issues, and some modules aren’t connecting properly. I took a log at the logs, but - I’m now out of my league. I posted the debug log below and the PM2 error log below that. Any ideas?

0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ]
2 info using npm@6.14.12
3 info using node@v10.24.1
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle magicmirror@2.22.0~prestart: magicmirror@2.22.0
6 info lifecycle magicmirror@2.22.0~start: magicmirror@2.22.0
7 verbose lifecycle magicmirror@2.22.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.22.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/Magic
Mirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle magicmirror@2.22.0~start: CWD: /home/pi/MagicMirror
10 silly lifecycle magicmirror@2.22.0~start: Args: [ ‘-c’,
10 silly lifecycle ‘DISPLAY=“${DISPLAY:=:0}” ./node_modules/.bin/electron js/electron.js’ ]
11 silly lifecycle magicmirror@2.22.0~start: Returned: code: 1 signal: null
12 info lifecycle magicmirror@2.22.0~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.22.0 start: DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid magicmirror@2.22.0
15 verbose cwd /home/pi/MagicMirror
16 verbose Linux 5.10.103-v7l+
17 verbose argv “/usr/bin/node” “/usr/bin/npm” “start”
18 verbose node v10.24.1
19 verbose npm v6.14.12
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.22.0 start: DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
22 error Exit status 1
23 error Failed at the magicmirror@2.22.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

/home/pi/.pm2/logs/mm-error.log last 50 lines:
0|mm | Gdk-Message: 09:29:00.091: electron: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
0|mm |
0|mm | XIO: fatal IO error 11 (Resource temporarily unavailable) on X server “:0”
0|mm | after 34753 requests (34751 known processed) with 0 events remaining.
0|mm | npm ERR! code ELIFECYCLE
0|mm | npm ERR! errno 1
0|mm | npm ERR! magicmirror@2.22.0 start: DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
0|mm | npm ERR! Exit status 1
0|mm | npm ERR!
0|mm | npm ERR! Failed at the magicmirror@2.22.0 start script.
0|mm | npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
0|mm |
0|mm | npm ERR! A complete log of this run can be found in:
0|mm | npm ERR! /home/pi/.npm/_logs/2023-02-08T14_29_00_205Z-debug.log
0|mm | [08.02.2023 09:29.30.907] [WARN] You’re using a full whitelist configuration to allow for all IPs
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to retrieve device information
0|mm | MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load driver: kms_swrast
0|mm | MESA-LOADER: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:$${ORIGIN}/dri:/usr/lib/dri)
0|mm | failed to load swrast driver

I changed the tableClass for the weather module - I’m using both the “MMM-OpenweatherMap” and the “weather” modules - and my line spacing (the “leading?”; the space between the lines) is huge, regardless of what tableClass I use. I notice in the example photo that the spacing is huge there, too.

I messed with the line-height in main.css on the .xsmall style, but that doesn’t seem to impact what’s going on here.

I’m all for people learning and solving their own problems, but I’m perplexed on this, and maybe - since the example photo shows the same thing - this just isn’t addressable yet? Can somebody buy me a vowel, here?

Thanks!