Fixer service starts the maintenance mode every five minutes, but doesn't do anything about nextcloud-snap HOT 4 CLOSED

@Pajkastare welcome and thanks for your request

please run the debugging script and post results here

I think I recall that the Nextcloud "cron" interval could be changed using nextcloud.occ, but I don't remember the syntax right now.

see managing cron

from nextcloud-snap.

@Pajkastare just found this #2349 (comment) in one of your older issues, did you disable preview generator as suggested? assuming this is an upgrade issue as before.

• revert
• disable preview generator
• upgrade
• re-enable preview generator

see FAQ's

from nextcloud-snap.

@Pajkastare just found this #2349 (comment) in one of your older issues, did you disable preview generator as suggested? assuming this is an upgrade issue as before.

I did not do anything to previewgenerator prior to doing the upgrade (only sudo snap refresh nextcloud, no other preparation). Nevertheless, I did disable it (sudo nextcloud.occ app:disable previewgenerator), but the maintenance mode problem persisted.

@Pajkastare welcome and thanks for your request

please run the debugging script and post results here

I think I recall that the Nextcloud "cron" interval could be changed using nextcloud.occ, but I don't remember the syntax right now.

see managing cron

Thanks for the links - Regarding cron, I had apparently alreday set it to 24h (sudo snap get nextcloud nextcloud.cron-interval), but the fixer script runs every five minutes. This got me digging, since it was obviously something other than the cron service that started the fixer script all the time.

It appeared it was another cron job recently created by myself, which started/stopped nextcloud if the external storage (which I access via Samba and mount under /mnt/, since the disk performance on the Raspberry Pi was too poor for running Nextcloud well enough) was available/unavailable, and that cron job called "snap start nextcloud" even if it was already running. I fixed it to do nothing if Nextcloud was in fact running, and the maintenance mode problems went away.

So, today I learned that the fixer service is called every time the Nextcloud snap starts, and that running snap start $NAME_OF_SNAP runs all startup code for that snap even if it was already running.

In other words, let's close this issue, it was my own fault, thanks for the help and sorry for wasting your time.

from nextcloud-snap.

Problem not related to the Nextcloud snap. (Erroneously believed that calling "snap start nextcloud" would not do anything if Nextcloud was already running, but the fixer service will be executed anyway.)

from nextcloud-snap.