Posts made by ember1205

Makes sense… Are there plans, then, to change the startup to a single command (script) that will read some sort of config file or accept a command-line parameter to control what gets started? I had to do a bit of digging to find the different (correct) commands to use to start the server on a headless machine and the client on a Pi and then put them into the “mm.sh” startup script so that PM2 could load each of them correctly. This doesn’t seem to match up with what’s documented, either.

In the main configuration file, there is a section to specify “serveronly” as an option which is supposed to NOT load any client resources. Attempting to start the mirror with npm start doesn’t seem to actually “respect” this option and it constantly complains about client-side components that may not be installed or operational.

I’ve also not found anywhere in the configuration where you might be able to specify “clientonly” and indicate the server to connect to. Why is this? Why do I need three different ways of starting the mirror depending on if I’m running a server, a client, or both?

What am I missing here?

After a LOT of different attempts at upgrades, fail-backs, new installs, etc., I believe I finally corrected the issue…

It appears that PM2 was either somehow corrupted during an update attempt or just simply too far out of date. Attempting to run PM2 with certain command options (like stop or even status) was resulting in errors indicating some sort of circular reference. After doing a forced upgrade to the latest version, it stopped showing these errors and the mirror is to running as expected.

I did make some additional changes that include copying the core MM directory off to another linux host where I now run the mirror as a server. The RPi is now purely a client and it loads noticeably quicker as a result.

Pretty sure it’s an out of memory issue. Once it crashes, the free memory jumps way up then trends back down once it restarts.

I’ve also discovered that this seems to be purely a “client” problem as I can connect to the Pi from a remote machine using a web browser and it will run just fine without any hiccups while the local client on the Pi crashes about every 60-70 seconds which correlates to two load intervals for photos. Maybe the MMM-ImagesPhotos module isn’t releasing memory properly?

The device is restarting for what appears to be out of memory / swap space issues. Every time the system crashes and restarts, /dev/shm is at zero available space.

This location appears to be where the processes are storing content from the image files that are being loaded and it’s apparently causing something to overrun the available space. I have added images, but that was a couple of weeks ago (before even applying the OS updates) and everything ran perfectly fine.

Forgive me, but “can’t do” what, exactly?

I have reverted to the exact software, install, and configuration that was in place before running the upgrade by renaming the upgraded directory and then renaming the backed up directory back to the original name. Unless there are files downloaded and stored -outside- of the MagicMirror directory, this should have ensured a complete reversion to the working files.

Umm… git stash pop?

I renamed the upgraded install to “MM-Upgraded” and then renamed my copied directory back to “MagicMirror”. Neither of them works properly at this point and the copied directory was never touched during the upgrade process.

Email sent…

pi 3B+

uname -a output

Linux raspberrypi 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux

How do I post the log? Far too large to go into a post, and isn’t a support file type to attach.

Error on my part… I still have the upgraded directory.

There is no info from the logs that I can tell that shows any sort of crash or anything. And the line from the npm logs just shows the run-start.sh command.