Server: Happens on every Update, so does on update from 13.0.6 to 14.0.1

[cpu2910]

Update failed with message:
notifications: Failed to enable app notifications

notifications app wasn't enabled before the update.

I reported this issue many time before, but nothing happened.

And I bet that the error happened on the next update again...

[violoncelloCH]

without filling in the issue template, we can't even try to reproduce your issue
please give some detailed information

[nextcloud-bot]

GitMate.io thinks possibly related issues are https://github.com/nextcloud/server/issues/8912 (Upgrade from 12.0.6 to 13.0.1 failed), https://github.com/nextcloud/server/issues/8894 (GUI: No update available from 12.0.6 to 13.0.1), https://github.com/nextcloud/server/issues/6039 (Update from 12.0.0 to 12.0.1), https://github.com/nextcloud/server/issues/8969 (theming app not working after update from 12.0.6 to 13.0.1), and https://github.com/nextcloud/server/pull/10932 (13.0.6).

[cpu2910]

Sorry, here's some more info:

It's the same error as #6140 and #10453, both reported by me and describing the same behaviour.

Server configuration
debian 9.5 stretch

Apache 2.4.25

Maria-DB 10.1.26

PHP 7.0.30

14.0.1 (after the update)
Updated from 13.0.6

From the log:
Error | notifications | OC\HintException: Failed to enable app notifications-- | -- | --

That's all.
The notification wasn't enabled before the update and isn't after the update.

All other features in my nextcloud are running fine.

My suggestion: Check whether the notification is enabled before the update and do not try to activate it when not necessary?

[kesselb]

You are running into this case
https://github.com/nextcloud/server/blob/483ad01a0933751732d84f40fab61c45050a7fa8/lib/private/Installer.php#L552-L558

Installer tries to enable the app but table already exist. Could you check your database server for a table notification or notifications_pushtokens. If the app is disabled but these exist something went wrong.

If these tables exist i would create a backup before the next update, delete the tables (only notification and notifications_pushtokens), run update and see what happens :smile:

You could try php occ app:enable notifications and php occ app:disable notifications? Maybe there is some helpful output :see_no_evil:

[cpu2910]

There is an empty table named 'oc_notifications'. Could it be this one?

Then I'll try with the next update...

[kesselb]

There is an empty table named 'oc_notifications'. Could it be this one?

Yes

[cpu2910]

Thank you, I'll report after next update.

[cpu2910]

Today I dropped empty table 'oc_notifications' from the database.
Then updated from 14.0.1 to 14.0.3 and the update runs flawlessly.
Thanks for your help!