-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WORKAROUND] NC14 RC2: occ upgrade hangs on running cronjob it states #10949
Comments
GitMate.io thinks possibly related issues are #6960 (occ upgrade is outdated), #10918 (Occ Upgrade forces to run once a day), #9562 (Check before running "upgrade" if cronjob is still running and wait for it to finish), #8092 (Upgrade notice should not be displayed when occ is run with --output=json), and #4726 (Upgrading Nextcloud sometimes causes Cronjob Deadlocks). |
Try to change your current version in [nextcloud path]/config/config.php to a lower version. In my case i've changed 14.0.0.17 to 14.0.0.0 |
See #9992 for more information about this issue |
@snopy234 I ran into the same issue. Changing version in |
disabled the nextcloud cronjob |
@awrede nice to hear that it's working :) |
Thanks, this ben Worked, Working, yes Working... THX! |
This issue is still present in 14.0.1 and the workaround is the same. |
Is my workaround still working? I havn't any problems since i changed the version |
@snopy234 👍 |
Workaround does not work for me:: Here the bookmarks app causes the trouble, but before the activity and accessibility app caused the problem. I disabled them. How to go on? PS: Nextcloud causes trouble at almost every update. As much as I like it, it would be great if the update process would me much more robust. |
Disabling files_external_gdrive did the job... (wasn't there a time when nextcloud disabled all but the core apps by itself before updating?) |
I hadn't activated that plugin, so the cause of your trouble was different. |
Also got this after the 14.0.1 upgrade. The workaround from @hchristo worked |
Killing the cron job caused the trouble actually here, because we store a "is something running" timestamp for each cron job and it only get updated by the job itself once it finished. The cronjob also just finishes the currently running one and then updates the DB table. Best would be the SQL query from #9992 (comment), but be aware that if the cron.php is still running somewhere that this could cause some issues. |
Also this would be helpful to fix the cause of this issue:
|
@cvandesande which workaround from @hchristo do you mean? |
@snopy234 where you downgrade the version in config.php to 14.0.0.0 |
Same issue. Query (@MorrisJobke):
Also tried updating Nextcloud manually, following this guide: https://docs.nextcloud.com/server/13/admin_manual/maintenance/manual_upgrade.html - with the same result: stuck, waiting for cron to finish. Is there an hotfix to get Nextcloud working again? |
Fixed it by setting the results of the query |
cc @rullzer for the background job in previews :/ |
Hi all, I also have this issue.
today, upgraded from 14.0.1 to 14.0.2 and also got it. Feedback/Edit : solved by doing SELECT * FROM oc_jobs WHERE reserved_at <> 0; Thanks |
Saw this error for the first time when upgrading from 14.0.2 to 14.0.3 with commandline updater.phar. Solved by changing version to 14.0.0.0 in config.php |
How to do this please give in detail here (For novice user) This error occured during 14 ---> 14.1 & now 14.1 -----> 14.2 |
See my comment in #10949 (comment) |
Hi all Solved (again) it by looking in the oc_jobs table, found the line with field reserved_at <> 0, and set it up back to 0. Thanks |
Hi, |
The big question is, why there are those entries. What type of cron job do you have? Do you run them in |
I just use the Cron option for background jobs. Could it be related to the News App? I reinstalled that before I updated the nextcloud instance. I know from experience that News takes a long time to update after installing a new version because it happens dat my feeds aren't accessible for hours. And since this app also uses cron for updates, could it be that it is holding up something. Just guessing... But can I check this Cron update behaviour somewhere in the logs? Running this nextcloud instance on an RPI3... |
Not really - except it is a news background job, but it seems to be many different ones in here. |
I also use cron (provided by debian stable package) and have the news app installed |
Sorry for bumping, just got this on one of the servers I maintain going from 14.0.1 -- 14.0.3.
All good now. |
Any idea how to get rid of this? I'm kind of sick of going into manual mode to repair NC after every update. Please please make the updates more robust!! |
Meet the same issue during update to 14.0.3 |
We removed this via #12188 Will be shipped in 14.0.4 |
@snopy234 Worked indeed! |
Thank you to share this with us @sscholl and @benneti :) btw i found the solution for the update error from 15 beta 2 to 15 rc 2 ... what are you doing with the updater at each update @nextcloud-bot @karlitschek :( |
I cant give to much info right now due to lack of time but this is the command line output of the upgrade process:
sudo -u www-data php /var/www/nextcloud/occ upgrade
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Set log level to debug
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
Waiting for cron to finish (checks again in 5 seconds) …
A cronjob was running at that time, killed the cron process but occ upgrade keeps giving this output.
When im home I provide more info (mysql/php7/etc..).
Tell me what else you need apart from the template. I use my own upgrade script. perhaps that might help.
to be continued...
Cheers
The text was updated successfully, but these errors were encountered: