How to upgrade a Linux "server" with minimal modules?

ember1205

The only thing is puts on the screen of any potential interest is

[ -f node_modules/.bin/husky ] && husky || echo no husky installed

sdetweil

@ember1205 what MM version is this?

ember1205

@sdetweil I reverted back again (Leap 15.6)

I recall seeing a 36 or something somewhere if that helps.

I had even moved the MM folder off and tried starting again, re-installed npm 22 and 24, and the errors were exactly the same. Something is out-of-whack somewhere and I haven’t had the time to dig deep enough to understand if it’s MM, my linux machine, or a combo.

I’m considering trying a fresh Leap 16 build and seeing what happens. If that works without an issue, then at least I know “it’s possible.”

sdetweil

@ember1205 mm version is in package.json

2.35/2.36
all custom.css stuff moved to config folder (user managed files go here)
default modules moved from modules/default to defaultmodules

ember1205

@sdetweil As mentioned, I reverted… back to whatever I was previously running.

Working on a fresh Leap 16 install, fresh MM install. Running into problems with inability to connect to display (running serveronly, no display connected). Seems that the serverOnly config setting may not get used any more? I have to start the server with “node --run server” to get past the display errors.

BTW… fresh install, there is no ‘default’ directory under modules… Thoughts?

sdetweil

@ember1205 said:

BTW… fresh install, there is no ‘default’ directory under modules… Thoughts?

default modules moved from modules/default to MagicMirror/defaultmodules

“server”: “node ./serveronly”

looks like a bug in 2.36 , fixed in 2.37-develop

3 more weeks til 2.37

you could get develop branch
https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

ember1205

@sdetweil The bug may have been around for a while… my mm.sh script is launching the mirror via “npm run server” and that script is what pm2 uses to launch the mirror. I’ve been doing it that way for a long time, likely because the serverOnly config setting wasn’t working.

If I actively run “npm run server” and then do “ps aux |grep node” I do not see anything related to node18 in the process list.

sdetweil

@ember1205 said:

likely because the serverOnly config setting wasn’t working.

the serverOnly config only works with my run-start.sh script,
and was removed from the sample config.js a good while back.

for the node 18 thing,
if you disable the extra modules (make a new config.js, or use the sample, and use the env variable

export MM_CONFIG_FILE=config/filename

to test

do you ses the same message?

ember1205

@sdetweil I don’t believe it’s the modules.

Leap 16 fresh install is fine with a fresh MM install as well. I upgraded the server again from Leap 15 to Leap16. Before the upgrade, I removed node and npm modules linked to version 18 and MM was running fine in all mannners.

After the upgrade, I made a couple of system-level changes (like disabling the firewall that it forces on you) and added the node/npm modules for version 24 and wasn’t able to start the mirror with pm2 like normal… it continues to throw errors about node18 being missing. However, running the mm.sh script manually or launching the mirror via either npm start server or node --run server works fine.

Did more digging around and found that the issue lies solely in the hands of pm2… the back-end environment was created back in the node/npm 18 days and that was saved in the configuration. The only way to find it was to do a “pm2 dump” and scan the file.

Once I knew it was pm2 for sure, the actual fix was pretty simple:

pm2 save
npm install pm2 -g
pm2 update
pm2 unstartup
pm2 startup

If MM wasn’t still configured as a process…

cd ~
pm2 start mm.sh
pm2 save

I’m running on Leap 16, latest patches, node/npm 18 is uninstalled, mirror is properly auto-launching. Now, I can update the modules and the mirror… But not before I do a snapshot! lol

sdetweil

@ember1205 awesome info!! Thanks for the update

ember1205

@sdetweil

Do any of your scripts check for pm2 and update the version during any installs or upgrades? Seems like, for the latter at least, that would be helpful.

My original mirror was obviously built quite a long time ago as the node18 variable was linked to the startup process. No idea how many MM revisions I went through between then and now and was always running on the much older version of node no matter what I did to upgrade the main system.

sdetweil

@ember1205 the upgrade script does

ember1205

@sdetweil

I don’t see anything in the script to do the pm2 save or a “pm2 start mm --udpate-env” so that it would use the new version of node. Not sure if your script is already gracefully handling those kinds of updates for the MM startup.

Also, since the script seems to assume Debian-based distro’s, dpkg doesn’t execute on my system and I’m not entirely sure if the script would effectively update my system for me. Thoughts on that?

sdetweil

@ember1205 it is Debian based for sure.

Doesn’t work in lxc’s, or other container types, docker

The upgrade-script, starting on line 496 is the code for pm2 upgrade

That was also extracted to upgradepm2.sh
If you wanted to do it separately

sdetweil

Sorry, you were talking about refreshing the application defs on pm2.

No, dont do that, never seen any side effect til now

Will add it to the work list here
https://github.com/sdetweil/MagicMirror_scripts/issues/125