Is there any additional information in the appcenter logfile /var/log/univention/appcenter.log
Please post anything regarding the app update from that file. Is there anything manually configured in your app setup? Manually edited config files, additional owncloud apps, …?
If the execution of the setup script inside the docker container just stopped, the container itself may have been stopped.
There probably is no current owncloud container after the update failed, you can check for one with docker ps -a
If there is one, try starting it with docker start <containername> otherwise, try reinstalling the app. If that does not work either, install the app with univention-app install owncloud --do-not-revert and check the owncloud docker container logs with docker logs <containername>
“SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘owncloud.oc_appconfig’ doesn’t exist in /var/www/owncloud/lib/composer/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php:53”
Upgrading server database…
An unhandled exception has been thrown:
PDOException: SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘owncloud.oc_appconfig’ doesn’t exist in /var/www/owncloud/lib/composer/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:104
Is the actual owncloud database still available? You can connect to MariaDB on UCS via e.g. mysql -uroot -p$(</etc/mysql.secret), then something like use owncloud; show tables;
If there is something missing, maybe there is a hint in the appcenter.log while the app update was happening? I am still trying to figure out what went wrong on your UCS system. I am repeating an earlier question: Is there anything manually configured in your app setup? Manually edited config files, additional owncloud apps, …?
You may be able to restore the database. The owncloud app creates a database backup on app updates, which can be found at /var/lib/univention-appcenter/apps/owncloud/data/backup/
The owncloud db is there - but there are no tables. I’ll restore the backup. Fingers crossed. There’s no manual stuff going on with my owncloud by the way.
Had the same issue but chickened out by restoring VirtualBox snapshot. Guess I will stay on current version till issue is fixed. To be clear, I hit the “upgrade” button in the app center. Not sure this is the same or the only way to do the update…
So, you have the owncloud app installed, please verify this via univention-app info, and the database is restored. Which error do see in the docker logs when you try to start the app containers? A quick way to do so is service docker-app-owncloud start
EDIT If that does not work, you should be able to uninstall the app with univention-app remove --do-not-backup owncloud
My issue is now resolved. Thanks for all the pointers. It turns out that zimbradrive (which we are not using!) was enabled and this breaks the update. Anyone in the same boat - if you can quickly get into the shell on the docker - enter occ app:disable zimbradrive
Hi Neal,
I never used Zimbra. How and where did you notice it was enabled? And (shame on me) how do you get into the shell on the docker? Is it different than the main command line?
Thanks
Claudio
Thanks @tpfann. I do not have zimbradrive at all. Nevertheless, I looked at the list of apps (below). Any one you think might be breaking the update for me?
I can not comment on which owncloud app might break the app update, because i don’t know. I am working for Univention, the app is maintained by ownCloud. They know about the issue that certain activated apps may stop the app update and there is a plan to work on this in a future app update.
I know that the apps that come with the default installation do not cause any issues, so i would deactivate all apps you installed manually before starting the update. As always, a backup or snapshot is helpful in case something goes wrong.
