Hi,

Investigating crashes and freezes, etc, can be very difficult.
When everything is running fine and you collect data, you will see that everything is more or less okay.
When it crashed or is frozen, you are too late.

Since a few weeks I had the problem that my MM was frozen and I could not enter any commands or a command took painstakingly long to return output.
A command like top was out of the question for example.
Using a script running as a cron job, I was able to identify a memory issue with electron.js.
I then decide to use a usb stick on which I created a swap device.
Since then my MM is not freezing anymore.
And I am able to see electron.js using up my memory and sometimes I see spikes in CPU usage.

Mind you, that crashing is something different then freezing, but the tools to use are more or less the same, provided the MM application or a MM module is not the culprit.

My script to check memory usage, very basic and simple:

pi@MagicPi:~ $ cat top.sh
#!/bin/sh

date >> /home/pi/top.txt
top -b -o +%MEM | head -n 22 >> /home/pi/top.txt
echo "=============================================" >> /home/pi/top.txt

The cron job:

00,05,10,15,20,25,30,35,40,45,50,55 * * * * /home/pi/top.sh >/dev/null 2>&1

%CPU will sort on CPU usage.

Concerning swap space, top will show the usage, but this gives a quick view:

$ free -h

Swap details via:

$ swapon -s

There are many more commands and settings to look at, but one has to start somewhere :-)

Good luck.

@Clubjack and others,

I noticed this problem too.
For instance my birthday lasted 2 days ( only got presents once though) and my wedding-day is one day forward (which will upset my wife).
The entries were made using Google Calendar (so not a calendar app that synchronizes with Google).
I notice this since 2020, but that does not mean it did not happen before, could have overlooked it.
When I ran a test with a dummy entry, it worked fine.
When I toggle a „faulty“ entry from repeating to not repeating and then back to repeating, the entry is shown correct.
I collected some data and will post it when I sorted it out a bit.

@sdetweil

My Google Calendar remark was more aimed at the basic.ics we get from it.
I see now it added an unnecessary discussion.
However it did take me some time to find out that the screen you showed is only seen after clicking the More Options button; my bad.

Your evaluation of showEnd and showEndsOnlyWithDuration is quite useful.

Btw, one time in the Dutch parliament there was a big confusion about voting for something.
If you do not want XXX, then vote yes, if you want XXX then vote no.
Of course this went wrong.

Concluding: all my tests passed, meaning it works as designed.
I will raise an issue for a feature request, but you can either reject it or put it on the bottom of your list of todo’s.

Okay, this calls for some more basics.

Print the whole file:
$ cat top.txt

Load the file in an editor:
$ nano top.txt
$ vi top.txt

I am old-school, so I use vi, but nano is more Word-like.

To show the last 50 lines:
$ tail -50 top.txt

To show the first 50 lines:
$ head -50 top.txt

Where of course 50 is just an example.

To show text that is appending:
$ tail -f top.txt

To show text that is appending and re-open the file when necessary (useful for rotating log files):
$ tail -F top.txt

On disabling a module see the next reply.

@sdetweil said in pm2 Autostart invert issue:

@Ethyx r u running buster?

try this
https://pimylifeup.com/raspberry-pi-rotate-screen/

@Ethyx

Did you try this?

display_hdmi_rotate=2

Make sure you only have one of the options active; not that you rotate a rotated screen. :-)

@mumblebaj said in Contributing to a GitHub repository - a bit stuck:

Make sure it is set to bash.

It is set to zsh.
No issue to change it to bash, but is there a reasoning behind it ?

Stupidly enough I had this Terminal open the whole time.

I just did ‘Commit’ from within VS Code and then did ‘Sync Changes’.

Result:

% git status
On branch evroom
Your branch is up to date with 'origin/evroom'.

nothing to commit, working tree clean

So that works just fine.

I also made a change using the Terminal and then did the add and commit from the Terminal.
In the Source Control pane you can see what you do on the command line in real time.

To disable MMM-WatchDog, edit the config.js file.
Locate:

module: 'MMM-WatchDog',

Edit this like this:

module: 'MMM-WatchDog',
disabled: true,

and restart MM:

$ pm2 restart mm

Use

pm2 list

to check if your application name actually is mm, or something else.

Later you can enable it again by updating config.js like this:

disabled: false,

This works for all modules.
When I test modules I normally leave the config lines and disable a module in this fashion.

@Sam-0

So as stated before you most probably need to change wayland-1 to wayland-0 in your scripts.
Give it a try.
Furthermore the .lock file may cause a problem, but I guess this will show in your error log.
And temporarily change the times in your cronjob to speed things up a bit.
Waiting till ten and midnight is not really necessary :-)

@richland007
On pm2 and restarting I cannot say many.
On using ctrl+q neither, as I only access my MM via ssh.

Can you send the output of the following commands:

$ uname -a
$ swapon -s
$ free -h
$ cat /etc/dphys-swapfile | egrep -v ‘#|^$’
$ sudo service dphys-swapfile status

I just learned that swap is handled as a service.
Being old-school, this is something new to me :-)

@Peter

This is my config for de Eredivisie.
It shows the first 9 teams from the standings and focuses on one team.

{
  module: 'MMM-soccer',
  disabled: false,
  position: 'top_right',
  config: {
     api_key: 'your_api_key',
     colored: true,
     show: 'NETHERLANDS',
     focus_on: {
       "NETHERLANDS": "AFC Ajax",
     },
     max_teams: 9,
     logos: true,
     leagues: {
        NETHERLANDS: 'DED',
        EUROPE: 'CL',
     }
  }

There are no logos for de Eredivisie included, so you will have to collect them yourself.
They need to be placed under:

/home/pi/MagicMirror/modules/MMM-soccer/public