Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About uberchuckie

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Having the MariaDB log file is useful. I'm not sure if the problem is the same as the others are having but the symptoms are the same where MariaDB is not starting. The problem here is the redo log is preventing the MariaDB to upgrade from 10.4 to 10.5. You can try reverting to image tag 2.0.2, shutdown and see if the redo gets processed properly then move the latest again. The other thing you can try is to just delete the /config/databases/ib_logfile* before trying to start the container. You may potentially lose transactions that were not committed but that's probably fine.
  2. Nothing jumps out at me as the problem right now. Maybe it's failing to start because it can't create the <docker id>.err file? I haven't been able to reproduce the problem on my server.
  3. Nothing looks out of the ordinary. It's strange that the database log file doesn't exist. Maybe it can't create it and that's why it's failing? What version of unRAID are you running? It looks like MariaDB is running fine during the schema creation but the service won't start after it shuts down and restarted. Can you run /usr/bin/mysqld_safe --skip-syslog --datadir='/config/databases' in the container console? I can't reproduce this problem on my server.
  4. @Fiala06 MariaDB appears to be in a restart loop. Can you post the /config/databases/9ac22bf8d797.err log to show why it's failing to start?
  5. @seanwalter Can you post the contents of the /config/databases/observium.err log file? That will tell us why MariaDB is not starting.
  6. @seanwalter I pushed a change to always fix up the permissions before staring MariaDB. It didn't break anything for me and the permissions are set to nobody with 755 permissions. Backup your database and give the dev tagged image a try? I'll push 2.1.2 if it fixes it for you.
  7. This should be safe to run as it's already the last step of the MariaDB script when it's creating a new database. I'll test it out when I have time.
  8. It looks like file permission problems. Here are my file permissions. Creating the database files from scratch, I see the following permissions Can you post your config permissions?
  9. @kimocal The embedded MariaDB service was stuck in a restart loop. The /config/databases/ea65e1ef1086.err file should show why. I've had this error once before. MariaDB couldn't read the InnoDB files for me. Restoring from backups or creating the database from scratch resolved the issue for me. This image doesn't need privileged access and works without it.
  10. Check the nginx log and see what the error is. Did you define an upstream pool for observium? Try using the IP address instead for the proxy pass URL?
  11. I don't think alerts are supported in the Community Edition.
  12. Mine is 438MB with around 4 years of data from one device.
  13. The database hasn't been created yet. Did you stop the container before deleting the appdata volume for observium?
  14. Try deleting your observium directory under the appdata volume mount and start the container again. Let the database initialization script run to its completion.
  15. I took a look at this... I ran /opt/observium/poller.php -d and saw this: ##### Timezones info ##### o Date Tuesday, 10-Dec-19 21:08:21 EST o PHP -05:00 o MySQL -05:00 This looks like it's correct and PHP and MySQL have matching time offset. root@c3b53bf2ea0d:/opt/observium# mysql -u observium -p observium Enter password: Reading table information for completion of table and column names You can turn off this feature to get a quicker startup with -A Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 16 Server version: 10.4.8-MariaDB-1:10.4.8+maria~bionic-log mariadb.org binary distribution Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [observium]> select now(); +---------------------+ | now() | +---------------------+ | 2019-12-10 21:11:56 | +---------------------+ 1 row in set (0.000 sec) MariaDB [observium]> This is also showing the correct time. I even tried adding "default-time-zone='-05:00'" to "/etc/mysql/my.cnf" and restarting the database and that didn't make any difference. The graphs are still in UTC. I'm not sure what's the problem at this point.