Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Oppaunke

Members
  • Joined

  • Last visited

Everything posted by Oppaunke

  1. May it help others: I restored an Appdata backup and edited the custom.cnf file by adding the entry „innodb_log_files_in_group = /config/logs“ which created two new log containers and enabled the start of mysqld. The original files were corrupted due to my cache drive ran out of space caused by a vm...
  2. I managed to get into the webinterface by deleting the .../www/owncloud folder. But when I try to use the internal db as you describe I get the same `no such file or directory’ error, only in the webinterface. How can I really start over from scratch? Do I need a new docker.img? Since you obviously prepared an empty database to start out of the box and deleting appdata/ownCloud doesn‘t touch it: where is it located?
  3. So the database doesn‘t live inside the container, but somewhere more globally (you implied otherwise on page 1 of this post)? And perhaps other installations could make use of the same database and potentially mess it up? So: how do I set it up „properly“? Did I miss a guide, tutorial or something?
  4. @dlandonRe-Installation including removing the owncloud folder in appdata doesn‘t re-create the database?
  5. @dlandon Your OwnCloud docker ran fine for about a year. Other than auto-updates I had no reason to ever change something, but a few days ago my calendars stopped to synchronize. Checking the web interface for reasons I found this instead: Exception occurred while logging exception: Failed to connect to the database: An exception occured in driver: SQLSTATE[HY000] [2002] No such file or directory #0 /config/www/owncloud/lib/composer/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(429): OC\DB\Connection->connect() #1 /config/www/owncloud/lib/composer/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(389): Doctrine\DBAL\Connection->getDatabasePlatformVersion() #2 /config/www/owncloud/lib/composer/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(328): Doctrine\DBAL\Connection->detectDatabasePlatform() #3 /config/www/owncloud/lib/composer/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(623): Doctrine\DBAL\Connection->getDatabasePlatform() #4 /config/www/owncloud/lib/private/DB/Connection.php(145): Doctrine\DBAL\Connection->setTransactionIsolation(2) #5 /config/www/owncloud/lib/composer/doctrine/dbal/lib/Doctrine/DBAL/DriverManager.php(172): OC\DB\Connection->__construct(Array, Object(Doctrine\DBAL\Driver\PDOMySql\Driver), Object(Doctrine\DBAL\Configuration), Object(Doctrine\Common\EventManager)) #6 /config/www/owncloud/lib/private/DB/ConnectionFactory.php(145): Doctrine\DBAL\DriverManager::getConnection(Array, Object(Doctrine\DBAL\Configuration), Object(Doctrine\Common\EventManager)) #7 /config/www/owncloud/lib/private/Server.php(493): OC\DB\ConnectionFactory->getConnection('mysql', Array) #8 /config/www/owncloud/lib/composer/pimple/pimple/src/Pimple/Container.php(113): OC\Server->OC\{closure}(Object(OC\Server)) #9 /config/www/owncloud/lib/private/AppFramework/Utility/SimpleContainer.php(111): Pimple\Container->offsetGet('DatabaseConnect...') #10 /config/www/owncloud/lib/private/ServerContainer.php(87): OC\AppFramework\Utility\SimpleContainer->query('DatabaseConnect...') #11 /config/www/owncloud/lib/private/Server.php(1160): OC\ServerContainer->query('DatabaseConnect...') #12 /config/www/owncloud/lib/private/Server.php(370): OC\Server->getDatabaseConnection() #13 /config/www/owncloud/lib/composer/pimple/pimple/src/Pimple/Container.php(113): OC\Server->OC\{closure}(Object(OC\Server)) #14 /config/www/owncloud/lib/private/AppFramework/Utility/SimpleContainer.php(111): Pimple\Container->offsetGet('AppConfig') #15 /config/www/owncloud/lib/private/ServerContainer.php(87): OC\AppFramework\Utility\SimpleContainer->query('AppConfig') #16 /config/www/owncloud/lib/private/Server.php(1089): OC\ServerContainer->query('AppConfig') #17 /config/www/owncloud/lib/private/Server.php(547): OC\Server->getAppConfig() #18 /config/www/owncloud/lib/composer/pimple/pimple/src/Pimple/Container.php(113): OC\Server->OC\{closure}(Object(OC\Server)) #19 /config/www/owncloud/lib/private/AppFramework/Utility/SimpleContainer.php(111): Pimple\Container->offsetGet('AppManager') #20 /config/www/owncloud/lib/private/ServerContainer.php(87): OC\AppFramework\Utility\SimpleContainer->query('AppManager') #21 /config/www/owncloud/lib/private/Server.php(1359): OC\ServerContainer->query('AppManager') #22 /config/www/owncloud/lib/private/legacy/app.php(346): OC\Server->getAppManager() #23 /config/www/owncloud/lib/private/legacy/app.php(110): OC_App::getEnabledApps() #24 /config/www/owncloud/lib/base.php(579): OC_App::loadApps(Array) #25 /config/www/owncloud/lib/base.php(998): OC::init() #26 /config/www/owncloud/index.php(54): require_once('/config/www/own...') #27 {main} Looks like something very much internal to the docker. I tried (after backing up appdata) a forced update, to remove the container and cleanly reinstall it, changing the additional options, the network interface (since intermediately I had no access to the web GUI at all) - all without success. Any pointers, please?!
  6. Unraid version used is 6.6.3 stable. No fancy stuff installed, no crappy hardware, configuration all-straight-forward. In both cases there was no connection loss logged. I'm not willing to fiddle around with this risking my data. A fundamental point of dockerization is to isolate its processes from the host system. So either the docker is faulty or the system is unstable. Since everything else works fine, I have my eyes on the docker.
  7. Statement: I cannot recommend using this docker. Why? It crashed Unraid twice with a simple 1-folder 60GByte photo backup (no special gimmicks used) onto a local SMB share. What happened? The backup process started and after a few minutes (like 10-12) the web interface died "lost server connection... retry in...". After that I was unable to stop the docker, therefore I could not stop the array and was in the end forced to cold reboot+parity check... What I tried: to avoid cold reboot I followed the unraid-wiki instructions (https://wiki.lime-technology.com/Console#To_cleanly_Stop_the_array_from_the_command_line) of course I followed the video tutorial and read about duplicati on Unraid. Searching for a stable and working alternative now, pretty disapointed about Unraid for not having a "favored/built-in/well-proven/well-maintained" solution for a simple local backup in place (no cloud). A little more disappointed that a docker running on Unraid can easily tear down the whole system until complete unresponsiveness. This is NOT what I would call a "stable" system.
  8. Had a similar problem and have it again after each Plugin update (quite annoying, actually): svnadmin: error while loading shared libraries: libicui18n.so.56: cannot open shared object file: No such file or directory I solve this by doing a manual installation of the following package: icu4c-56.1-x86_64-2.txz Download, grab a terminal, cd to the file and execute: upgradepkg --install-new icu4c-56.1-x86_64-2.txz

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.