MMM-CalDAV

sdetweil

@caw ok now need to look inside modules

ls -laF /volume1/magicmirror/modules
and in the module folder
ls -laF /volume1/magicmirror/modules/MMM-CalDAV

we did not check INSIDE the MMM-CalDAV/service folder to see if there is an existing file that might be overwritten (with the wrong permissions)

caw

@sdetweil

it´s in the /volume1/docker/magicmirror/modules

sdetweil

@caw ok, the docker container is running as user/group 1000/1000

so Simon and users is neither of those

and linux permissions are a set of values, 3 flags per

user – this user number/name (Simon)
group --if the user is part of the named group (users)
other – permissions for any user NOT in the two choices above

the permissions shown

user = rwx // user can read( r) write(w) and execute(x)
group = r-x // group can read( r) and execute(x)
other = r-x // all others can read ( r) and execute(x)

or 755

if you fix the permissions to 757
user rwx
group r-x
other rwx

or 775 (probably better, not allow ‘any’ other…)
user rwx
group rwx
other r-x

then other (1000) will be allowed to write to the folder (service folder)

caw

@sdetweil

so the permission error is gone but the *ics is still not saved
LOG attached

sdetweil

@caw can you show all the calDAV messages…

last says fetching
but the prior says not found…

MMRIZE

@caw
I cannot say anything without the full log. But at the first execution, ics would not be written yet, (calendar module is so fast than CalDAV’s connection and parsing) so just wait for the next cycle to finish serving, or just stop and rerun MM. From the second execution, ics will be served.

caw

@MMRIZE
hi i´ve got it- it was the firewall blocking and the ics files are created and a test is shown

THANK YOU VERY MUCH!!! :)
maybe you can add the workaround for a tutorial for any Synology User :)

sdetweil

@caw add the workaround?

caw

@sdetweil i think some of the Synology users have the same issue with permissions an their nas

sdetweil

@caw this is really a docker on synology implementation issue. you created files needed by the docker container using an outside the container userid.

many modules use their folder as a cache storage location