updated installer script available for testing

[swvalenti]

@sdetweil that is correct, can I somehow delete this node process as I don’t even use that module anymore?

[sdetweil]

@swvalenti yes, somehow… I don’t know how it got added…

can u do a

pm2 status

[swvalenti]

@sdetweil

pi@raspberrypi:~ $ pm2 status
┌─────────────┬────┬───────┬────────┬─────────┬─────┬────────┬───────────┐
│ Name        │ id │ mode  │ status │ ↺       │ cpu │ memory │
├─────────────┼────┼───────┼────────┼─────────┼─────┼────────┼───────────┤
│ mm          │ 1  │ N/A   │ fork   │ stopped │ 176 │ 0%     │ 0 B       │
│ omx_stream1 │ 2  │ N/A   │ fork   │ stopped │ 61  │ 0%     │ 0 B       │
│ omx_stream2 │ 3  │ N/A   │ fork   │ stopped │ 0   │ 0%     │ 0 B       │
│ omx_stream3 │ 4  │ N/A   │ fork   │ stopped │ 0   │ 0%     │ 0 B       │
│ server      │ 0  │ 1.6.5 │ fork   │ online  │ 3   │ 0.4%   │ 40.0 MB   │
└─────────────┴────┴───────┴────────┴─────────┴─────┴────────┴───────────┘
 Use `pm2 show <id|name>` to get more details about an app
pi@raspberrypi:~ $ 

[sdetweil]

@swvalenti i would guess server

pm2 stop server

[swvalenti]

@sdetweil Awesome that worked thanks Sam!

[sdetweil]

@swvalenti cool… maybe I should dump out the ps -ef list if I find that problem…

[swvalenti]

@sdetweil So I renamed the old magicmirror folder and updated. Now the updates stripped modules and config.js. They are not in the new magicmirror folder at all…what gives?

[sdetweil]

@swvalenti this is not an update, it is a NEW install…

so you have to copy from the old mm folder to the new…

if u wanted to UPDATE then u should run the UPDATE script

https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testing

[swvalenti]

@sdetweil Well I am an idiot, so I can just delete the new MagicMirror folder and then run the update in the other?

[sdetweil]

@swvalenti yes… UPDATE just gets you the new MagicMirror version. currently 2.9.0