Aha-got it!

sudo rm -rf ~/.nvm
sudo rm /usr/local/bin/node
sudo rm /usr/local/bin/nvm
pm2 stop mm (not sure if I missed this earlier)
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)"

This installed fine, but gave me an error of an out-of-date npm version, so I ran:

sudo npm i -g npm

Then moved all my old modules and config file over to the new install and checked my node/npm versions:

pi@raspberrypi:~/MagicMirrorBackup/modules $ node -v
v9.11.2
pi@raspberrypi:~/MagicMirrorBackup/modules $ npm -v
6.5.0

So they’re not as up-to-date as my previous ones, but MagicMirror is working fine!

Thanks everyone for the input, turns out just a bit of manual removal and persistence sorted me out!

Seems my reply to this got lost…

Got this working! Removed the .nvm directory, removed the symlinks, shutdown pm2 and re-ran the installation script and it all went in fine!

sudo rm -rf ~/.nvm
sudo rm -f /usr/local/bin/node
sudo rm -f /usr/local/bin/nvm
pm2 stop mm
sudo rm -rf ~/MagicMirror
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)"

I got an error on npm not being the right version, so upgraded that:

sudo npm i -g npm

(Note sudo is working now, which it wasn’t before) And now my node and npm versions look good and pm2 is running MagicMirror again!

pi@raspberrypi:/ $ node -v
v9.11.2
pi@raspberrypi:/ $ npm -v
6.5.0

Thanks everyone for the help!

@sdetweil said in Issues with pm2 in old mirror:

pm2 upgrade

That succeeded but didn’t fix the problem:

[PM2] Saving current process list...
[PM2] Stopping PM2...
[PM2][WARN] No process found
[PM2] All processes have been stopped and deleted
[PM2] PM2 stopped
[PM2] Spawning PM2 daemon with pm2_home=/root/.pm2
[PM2] Restoring processes located in /root/.pm2/dump.pm2
>>>>>>>>>> PM2 updated
┌──────────┬────┬──────┬─────┬────────┬─────────┬────────┬─────┬─────┬──────┬──────────┐
│ App name │ id │ mode │ pid │ status │ restart │ uptime │ cpu │ mem │ user │ watching │
└──────────┴────┴──────┴─────┴────────┴─────────┴────────┴─────┴─────┴──────┴──────────┘
 Use `pm2 show <id|name>` to get more details about an app
pi@raspberrypi:~/MagicMirror $ pm2 status
(node:5424) Warning: Accessing non-existent property 'cat' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:5424) Warning: Accessing non-existent property 'cd' of module exports inside circular dependency
(node:5424) Warning: Accessing non-existent property 'chmod' of module exports inside circular dependency
(node:5424) Warning: Accessing non-existent property 'cp' of module exports inside circular dependency
(node:5424) Warning: Accessing non-existent property 'dirs' of module exports inside circular dependency

Hello all! I’ve an old mirror setup that’s been running stably for about 3 years now, but it stopped working a little while ago. Since I last installed it via the auto-install script and isn’t an option anymore, I thought to start from scratch. I upgraded npm and node to the most current versions, but pm2 is erroring out when trying to launch:

pi@raspberrypi:~ $ pm2 status
(node:10537) Warning: Accessing non-existent property 'cat' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
(node:10537) Warning: Accessing non-existent property 'cd' of module exports inside circular dependency
(node:10537) Warning: Accessing non-existent property 'chmod' of module exports inside circular dependency
(node:10537) Warning: Accessing non-existent property 'cp' of module exports inside circular dependency

It looks to me like the node install is broken somehow, but I’ve no idea what might be broken:

pi@raspberrypi:~ $ node -v
v16.17.0
pi@raspberrypi:~ $ npm -v
8.19.2

Any thoughts?

Seems my reply to this got lost…

Got this working! Removed the .nvm directory, removed the symlinks, shutdown pm2 and re-ran the installation script and it all went in fine!

sudo rm -rf ~/.nvm
sudo rm -f /usr/local/bin/node
sudo rm -f /usr/local/bin/nvm
pm2 stop mm
sudo rm -rf ~/MagicMirror
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)"

I got an error on npm not being the right version, so upgraded that:

sudo npm i -g npm

(Note sudo is working now, which it wasn’t before) And now my node and npm versions look good and pm2 is running MagicMirror again!

pi@raspberrypi:/ $ node -v
v9.11.2
pi@raspberrypi:/ $ npm -v
6.5.0

Thanks everyone for the help!

Aha-got it!

sudo rm -rf ~/.nvm
sudo rm /usr/local/bin/node
sudo rm /usr/local/bin/nvm
pm2 stop mm (not sure if I missed this earlier)
bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)"

This installed fine, but gave me an error of an out-of-date npm version, so I ran:

sudo npm i -g npm

Then moved all my old modules and config file over to the new install and checked my node/npm versions:

pi@raspberrypi:~/MagicMirrorBackup/modules $ node -v
v9.11.2
pi@raspberrypi:~/MagicMirrorBackup/modules $ npm -v
6.5.0

So they’re not as up-to-date as my previous ones, but MagicMirror is working fine!

Thanks everyone for the input, turns out just a bit of manual removal and persistence sorted me out!

Now I’m trying to remove npm and nodejs to start again, but even after I’ve run apt-get remove npm nodejs I still get this:

pi@raspberrypi:~/MagicMirror $ which npm
/home/pi/.nvm/versions/node/v11.6.0/bin/npm
pi@raspberrypi:~/MagicMirror $ which node
/home/pi/.nvm/versions/node/v11.6.0/bin/node

@sdetweil said in Error on npm install:

@rmeskill looks like node is also downlevel

Do you mean I should upgrade it? this isn’t enough:

pi@raspberrypi:~/MagicMirror $ node -v
v11.6.0

@paddyhughes said in Error on npm install:

@rmeskill try do it in the MagicMirror folder
sudo npm i -g npm

Sudo still doesn’t work, but I tried it again just ‘npm i -g npm’ in the MagicMirror folder. Now I’m trying npm install again in the MagicMirror folder again, so I guess we’ll see, but it looks like it’s stuck at the same point as last time

@rmeskill said in Error on npm install:

Trying just with npm i -g npm instead…

Did give me a positive output:

Trying just with npm i -g npm instead…

Trying npm install again…

@paddyhughes said in Error on npm install:

I just installed a module and it asked me to update NPM think i did it in the root directory not MagicMirror one can be sure.
This is what worked for me
sudo npm i -g npm

sudo npm i -g npm didn’t work for me, got this error:

pi@raspberrypi:~ $ sudo npm i -g npm
/usr/local/lib/node_modules/npm/bin/npm-cli.js:85
      let notifier = require('update-notifier')({pkg})
      ^^^

SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:414:25)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Function.Module.runMain (module.js:467:10)
    at startup (node.js:134:18)
    at node.js:961:3

Trying just with npm i -g npm instead…

I’ve run npm cache clean --force also to no avail. And here’s the output of the .log file referenced in the initial error:

pi@raspberrypi:~ $ tail /home/pi/.npm/_logs/2019-01-06T14_26_53_131Z-debug.log
12308 http fetch GET 200 https://registry.npmjs.org/core-js/-/core-js-2.5.1.tgz 48668ms
12309 silly extract core-js@2.5.1 extracted to /home/pi/MagicMirror/node_modules/.staging/core-js-bce1a382 (63355ms)
12310 http fetch GET 200 https://registry.npmjs.org/clarinet/-/clarinet-0.12.3.tgz 60019ms
12311 silly extract clarinet@^0.12.0 extracted to /home/pi/MagicMirror/node_modules/.staging/clarinet-d9485acf (60537ms)
12312 http fetch GET 200 https://registry.npmjs.org/rxjs/-/rxjs-6.3.3.tgz 216457ms
12313 silly extract rxjs@^6.1.0 extracted to /home/pi/MagicMirror/node_modules/.staging/rxjs-ec2c3fab (217547ms)
12314 timing npm Completed in 9958812ms
12315 error cb() never called!
12316 error This is an error with npm itself. Please report this error at:
12317 error https://npm.community