@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

So I had a working copy of MagicMirror2 running on a Raspberry Pi 2, but I was running node at version 4.2 (I think, though it could have been npm that was complaining) so I finally bit the bullet and decided to upgrade. Now I’m running node v11.6.0 and npm v6.5.0, but when I try npm install && npm start in the MagicMirror directory, I get an error after it hangs for 30-60 minutes on one piece installing. It’s not always consistent on where it fails and I’ve tried multiple times to no avail. I’ve tried removing and reinstalling nodejs. I’ve tried copying away the MagicMirror directory and running the install script and everything fails at the same point. Here’s the output:

pi@raspberrypi:~/MagicMirror $ npm install && npm start
npm WARN deprecated time-grunt@2.0.0: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates.
Unhandled rejection Error: Command failed: /usr/bin/git clone --mirror -q git://github.com/patriksimek/vm2.git /home/pi/.npm/_cacache/tmp/git-clone-6428927c/.git
warning: templates not found /tmp/pacote-git-template-tmp/git-clone-1f4f605f
fatal: read error: Connection timed out

    at ChildProcess.exithandler (child_process.js:294:12)
    at ChildProcess.emit (events.js:188:13)
    at maybeClose (internal/child_process.js:978:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:265:5)

npm ERR! cb() never called!

npm ERR! This is an error with npm itself. Please report this error at:
npm ERR!     <https://npm.community>

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2019-01-06T06_19_57_831Z-debug.log

I should note the error appears to be due to a connection time-out, and I’ve checked my dns and pings work fine to the outside world. Does anyone have any thoughts?

Is there a way to add a custom page within the module? I’m specifically looking to add more coins of my own that you don’t include by default, but every time I do it gets overwritten by a pull.

I just realized I was making changes to the master simply in the css file vs the custom one-I’ve moved my custom settings to the custom file and that fixed that. However, I’m still having some issues with individual modules-I guess I’ll have to either write the dev team or create my own fork. If I create my own fork, though, how do I go about merging changes from the master to my fork?

So I’ve modified my Magic Mirror a bit. Within some modules I’ve made some changes to the main files to add functionality or just change the size of font that’s being used. I also added my own calendars to the calendar module. However, whenever I upgrade a module or my whole Magic Mirror it seems these settings are all overwritten. I’m sure there must be a way to only merge new changes or somehow save my changes with git versioning, I just don’t know how-can anyone make some suggestions or point me in the right direction of a tutorial? Thanks!

For anyone who’s having issues getting a graph to work for lesser-known/non-included, it relies on a proprietary ID value for a currency within coinmarketcap.com. In order to this to work you’ll need to find that value and define it within the MMM-cryptocurrency.js file.

Maybe there’s an easier way, but I got it working by going to coinmarketcap.com, finding the currency I wanted, then right clicking on the small inline graph and clicking ‘open IMAGE in a new tab’. That’ll come up with an url like this one for Dash: https://files.coinmarketcap.com/generated/sparklines/131.png.

Now, within the MMM-cryptocurrency.js file you’ll need to create a reference to this ID:

sparklineIds: {
                        bitcoin: 1,
...
                        dash: 131,
...
                        }

Reboot your mirror and all should work