Issue with pm2: a wild Memory Access Error occured (Speicherzugriffsfehler)
am using pm2 to start my Magic Mirror 2 instance - everything works fine for a year now (i only had one issue with the logs, but i found the flush command, so that is not a problem anymore) and all of a sudden my pi is stuck the Desktop… The Magic Mirror won’t start…
Every command with pm2 gives me: “Speicherzugriffsfehler” - it’s german and stands for Memory Access Error.
Besides that, the Pi works fine.
I am still able to download and install software. vnc viewer and putty are still working
I’m on an Raspberry Pi 3 Model B Rev 1.2 which is auto rebooting every day at 3 am.
The Report is not working either:
$ pm2 report
Read the web page for the instructions
Thank you @sdetweil
but sadly it did not work:
bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/fixuppm2.sh)" the log will be saved in /home/pi/MagicMirror/installers/pm2_setup.log bash: Zeile 188: 4212 Speicherzugriffsfehler sudo npm uninstall $up -g pm2 bash: Zeile 188: 4296 Speicherzugriffsfehler $pm2cmd delete MagicMirror > /dev/null 2>&1 bash: Zeile 188: 4342 Speicherzugriffsfehler $pm2cmd start $HOME/MagicMirror/installers/$PM2_FILE bash: Zeile 188: 4348 Speicherzugriffsfehler $pm2cmd save
“Zeile” = Row
“Speicherzugriffsfehler” = Memory Access Error
The log says:
pm2 setup starting - Fr Apr 10 14:28:47 CEST 2020 system is Linux mirrorpi 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.11 (stretch) Release: 9.11 Codename: stretch node version v12.14.0 force installing latest npm version via npm npm version pm2 installed pm2 installed, but does not work, uninstalling pm2 not installed, installing get the pm2 platform specific startup command startup command = pm2 startup command done configure the pm2 config file for MagicMirror start MagicMirror via pm2 now save MagicMirror pm2 config now pm2 setup completed - Fr Apr 10 14:36:37 CEST 2020
bummer. this is pointing to a bigger problem, SD cards are notorious for failing over time…
they have a fixed number of writable bits, but are write once… so that last place u wrote is marked as used.
when we start to see these weird behaviors, its been the SD card failing…