MMM-CalendarExt3 not syncing automatically with icloud

[MMRIZE]

@lightfixer2000
Nothing seems wrong. It seems just a sync timing issue. I don’t think it is the kind of issue to fix, but…
Your vdirsyncer may sync calendars at some point, and the calendar module fetches the change at another point (repeatedly in 10 minutes). CX3 will refresh itself at the other point (by default, every 10 minutes).
So when you change an event at some point, vdirsyncer may not have synced that event yet, or even if vdirsyncer synced successfully, the calendar module may not have fetched the event yet.
In the worst case, I think at least 20 minutes may be needed to reflect the change of event. It takes 2 cycles of CX3’s defaults.

Should it be the problem? I don’t think so. Calendar events are usually very stable and not frequently changed. Just waiting 20 ~ 30 minutes is an acceptable time for daily usage.

However, if you want a more urgent reflection of the change, shorten the period of sync/fetch/refresh of the 3 related programs(vdirsync, calendar module, CX3). But 99% of the process would be wasted with unchanged, same events,

[lightfixer2000]

@MMRIZE
Hi, Thanks for your response.
The actual MM works well and the CalendarExt3 display’s ok. I will leave the calendar for a longer time to allow further syncs to take place.
Any thoughts on the errors that are being reported in the log?
Thanks

[sdetweil]

@lightfixer2000 said in MMM-CalendarExt3 not syncing automatically with icloud:

[3010:0324/105027.892355:ERROR:gbm_wrapper.cc(75)] Failed to get fd for plane

this is an electron reported ‘error’, but is really a warning. you can ignore it. we can’t hide it

[greedyvegan]

even though the module loads, I see this error all the time; even after a refresh.
Should I ignore it?

[MMRIZE]

@greedyvegan That is not an error, just warning you can ignore it.

[lightfixer2000]

@MMRIZE I’ve left the MMM Calendar running for a far longer period and sync has never occured.
I did some digging/reading on Vdirsyncer and located the journal, here’s what it has been recording over and over.

Mar 26 00:11:18 raspberrypi systemd[923]: vdirsyncer.service: Scheduled restart job, restart counter is at 2.
Mar 26 00:11:18 raspberrypi systemd[923]: Stopped vdirsyncer.service - Synchronize calendars and contacts.
Mar 26 00:11:18 raspberrypi systemd[923]: vdirsyncer.service: Start request repeated too quickly.
Mar 26 00:11:18 raspberrypi systemd[923]: vdirsyncer.service: Failed with result 'exit-code'.
Mar 26 00:11:18 raspberrypi systemd[923]: Failed to start vdirsyncer.service - Synchronize calendars and contacts.
Mar 26 00:26:18 raspberrypi systemd[923]: Started vdirsyncer.service - Synchronize calendars and contacts.
Mar 26 00:26:18 raspberrypi (irsyncer)[4142]: vdirsyncer.service: Failed to locate executable /usr/bin/vdirsyncer: No such file or directory
Mar 26 00:26:18 raspberrypi (irsyncer)[4142]: vdirsyncer.service: Failed at step EXEC spawning /usr/bin/vdirsyncer: No such file or directory
Mar 26 00:26:18 raspberrypi systemd[923]: vdirsyncer.service: Main process exited, code=exited, status=203/EXEC
Mar 26 00:26:18 raspberrypi systemd[923]: vdirsyncer.service: Failed with result 'exit-code'.
Mar 26 00:26:18 raspberrypi systemd[923]: vdirsyncer.service: Scheduled restart job, restart counter is at 1.
Mar 26 00:26:18 raspberrypi systemd[923]: Stopped vdirsyncer.service - Synchronize calendars and contacts.
Mar 26 00:26:18 raspberrypi systemd[923]: Started vdirsyncer.service - Synchronize calendars and contacts.
Mar 26 00:26:18 raspberrypi (irsyncer)[4143]: vdirsyncer.service: Failed to locate executable /usr/bin/vdirsyncer: No such file or directory
Mar 26 00:26:18 raspberrypi (irsyncer)[4143]: vdirsyncer.service: Failed at step EXEC spawning /usr/bin/vdirsyncer: No such file or directory
Mar 26 00:26:18 raspberrypi systemd[923]: vdirsyncer.service: Main process exited, code=exited, status=203/EXEC
Mar 26 00:26:18 raspberrypi systemd[923]: vdirsyncer.service: Failed with result 'exit-code'.
Mar 26 00:26:18 raspberrypi systemd[923]: vdirsyncer.service: Scheduled restart job, restart counter is at 2.
Mar 26 00:26:18 raspberrypi systemd[923]: Stopped vdirsyncer.service - Synchronize calendars and contacts.
Mar 26 00:26:18 raspberrypi systemd[923]: vdirsyncer.service: Start request repeated too quickly.
Mar 26 00:26:18 raspberrypi systemd[923]: vdirsyncer.service: Failed with result 'exit-code'.
Mar 26 00:26:18 raspberrypi systemd[923]: Failed to start vdirsyncer.service - Synchronize calendars and contacts.

It states it can’t find the vdirsyncer file which isn’t really a file but a symlink as per Beh instructions.

Here are my vdirsyncer service and timer files in case I’m missing something?

[Unit]
Description=Synchronize calendars and contacts
Documentation=https://vdirsyncer.readthedocs.org/
StartLimitBurst=2

[Service]
ExecStart=/usr/bin/vdirsyncer sync
RuntimeMaxSec=3m
Restart=on-failure

[Unit]
Description=Synchronize vdirs

[Timer]
OnBootSec=2m
OnUnitActiveSec=10m
AccuracySec=5m

[Install]
WantedBy=timers.target

I did the Clean but Hard Way install of vdirsyncer and it created a vdirsyncer_env folder which according to instructions keeps Python contained. Could this be the issue?
Thanks in advance.

[sdetweil]

@lightfixer2000 many python scripts require a virtual environment. using the venv command to load from from the folder the installer creates before executing any python script

[sdetweil]

@lightfixer2000 I try not to use services anymore as pm2 can launch anything, like my installer sets up for MagicMirror.

see the pm2 --help

[lightfixer2000]

@sdetweil Thanks. I have pm2 installed and it runs MMM at boot up. According to the timer file the first fetch is after 2 mins of program start. I still don’t see any update to the ics file.
I will read pm2 help is a config or something else with pm2 I should be using?

[sdetweil]

@lightfixer2000 pm2 start xxx

xxx can be a bash script
or an executable

if you the bash script the you can ha e multile commands and logic

pm2’s job is to start and run things and keep them running