seanwalter

I have also been having this problem since updating to 6.12. Was hoping 6.12.2 would finally resolve it. Diagnostics attached. For now I have this script in my /mnt/cache directory so that I can ssh into unraid and manually restart nginx (many thanks to someone who posted the main two command lines in another unraid forum, and some people at stackoverflow for the error-checking code...): #!/usr/bin/env bash pkill -9 nginx pkillexitstatus=$? if [ $pkillexitstatus -eq 0 ]; then echo "pkill exited normally with nginx killed" elif [ $pkillexitstatus -eq 1]; then echo "could not find nginx process to kill" elif [ $pkillexitstatus -eq 2]; then echo "syntax error in trying to kill nginx using \'pkill -9 nginx\'" elif [ $pkillexitstatus -eq 3]; then echo "fatal error using \'pkill -9 nginx\'" else echo UNEXPECTED fi /etc/rc.d/rc.nginx start nginxstatus=$? if [ $nginxstatus -eq 0 ]; then echo "nginx restarted normally with exit code " $nginxstatus else echo "nginx restart returned an abnormal exit code: " $nginxstatus fi home-raid-diagnostics-20230703-1316.zip

Just closing the loop on this for everyone... Sadly (?) this was user error. Some of my disks in fact have not been cooling to the restart temperature. I have changed the thresholds in the plugin settings and will report back if things are still not working. Many thanks to itimpi for reviewing my logs and letting me know this.

Thank you. I just sent you my diagnostics.

I am noticing unexpected behavior with this plugin recently. I am on version 2022.04.12. I use it to pause parity check when disks overheat (trust me, I've tried various cooling solutions...) Recently, I enabled "Use increments for scheduled parity check," with increments running between 2am and 6am daily and the scheduled check starting at 2am every Saturday. The behavior I get is that parity check starts at 2am on Saturday, runs until the disks overheat (15-20 min) and then permanently pauses. (I can manually resume, but it won't resume automatically) Attached are the current portion of the log file, the current .progress file, the current .progress.save file and a screen grab of my settings. I'll appreciate any help/advice on how I might get this to work as expected. Thanks! parity.check.tuning.log parity.check.tuning.progress parity.check.tuning.progress.save

Funny…After posting I went into docker hub to get the path to the prior version, and saw the latest update came through “4 minutes ago”. The update fixed it for me, too. Good times

I am having the same issue

@uberchuckie good news...updating my 2.0.2 container to 3.0_beta worked -- my data history is intact, I can connect via the web GUI using my user name and password, etc... It looks like others are having success as well, though to close the loop, I am using /mnt/cache/appdata for my observium config and other files. Thank you for sticking with us on this, and working through the issues!

I may have new news, but it's all a little weird... Because there was some discussion that these issues have to do with mariadb not updating within the docker container, on Friday I went ahead on a whim and ran an apt update and upgrade to all the packages from the observium:latest docker console. Several updates were pulled down -- not sure if that's normal for docker containers, as I generally don't get this far into it Following the updates, I started actually getting errors logged to my observium.err file per the reporting in the container log file. The error was: 2020-09-25 20:10:00 0 [ERROR] mysqld: File '/var/log/mysql/mariadb-bin.index' not found (Errcode: 13 "Permission denied") 2020-09-25 20:10:00 0 [ERROR] Aborting The file in question did exist. Permissions were 660. With permissions changed to 666 or 777 the error persisted, which seemed a little weird. The file in the log seems simply to reference another file in the same directory, mariadb-bin.000001, with the same 660 permissions. I also tried changing those permissions, but it didn't seem to help. I subsequently reverted back to 2.0.2. In writing this post now (~2 days later) I am seeing that in the 2.0.2 container, the files are owned by nobody:users, which is different from the owners that were showing up under the :latest container. In that container, the group was "adm" but I don't remember the user name. Next-level weirdness...I tried to repeat this entire process just now to get the user name again, but I could not reproduce the results -- after running the apt upgrades, things remained in the state where nothing was being logged to observium.err. Worse(?), the mariadb-bin files were not even being created in the container's /var/log/mysql directory. Finally, next-next-level weirdness, I decided I should create a second docker container to mess around with, using observium:latest. So basically I did a new install of the container, with a new container name, into a new appdata folder. When I had reverted back to 2.0.2 above, I had not deleted my apt upgraded :latest image file, so docker used that file to create the new container. And...this one works. Only problem is, all my data is in the 2.0.2 container. I can try to copy my 2.0.2 databases over, but I'd love any recommendations on whether this is a reasonable thing to do, and/or what exactly needs to be copied, and/or how to force a database conversion if one is necessary. With both containers now run-able, I am also happy to run other tests if helpful. Side note, my unRAID Docker page reports that the version is "not available" when I pull the container from uberchuckie/observium or uberchuckie/observium:latest. This is not an issue with uberchuckie/observium:2.0.2. I am slightly nervous there's an updated source on dockerhub and I missed the memo...

All, I encountered this problem for the first time today across most of my PCs, and the fixes in this thread did not work. What did work was adding a line to the [global] section of my unRAID smb extra configuration settings: client min protocol = SMB2 To be clear for those who are less versed in smb settings, this is in addition to a line I already had in there for the server, which is simply min protocol = SMB2. Note, I assume this change will break any SMB1 clients trying to connect, but hopefully those are increasingly few and far between. That said, I have not turned off the SMB1 client in my Windows features, though I assume it will no longer be necessary for accessing unRAID. I might test that later this week and report back with an update.

@uberchuckie, thanks for all your efforts to help troubleshoot this. Since it seems @Fiala06 and I are having similar issues, I went ahead and ran the mysqld_safe command in my console as well. I get the same result: root@observium:/# /usr/bin/mysqld_safe --skip-syslog --datadir='/config/databases' 200912 16:06:02 mysqld_safe Logging to '/config/databases/observium.err'. 200912 16:06:02 mysqld_safe Starting mariadbd daemon with databases from /config/databases However, if I run the same command using the 2.0.2 docker image (which still works for me), I get a different result: root@observium:/# /usr/bin/mysqld_safe --skip-syslog --datadir='/config/databases' 200912 16:09:58 mysqld_safe Logging to '/config/databases/observium.err'. 200912 16:09:58 mysqld_safe A mysqld process already exists Hopefully that helps a little.

So...not sure if this helps or not, but at present the latest docker in the main branch and the docker in the dev branch do not write to my observium.err file. The 2.0.2 version does. Here is the log from my last start/stop of 2.0.2, in case helpful: 2020-08-14 15:50:23 0 [Note] InnoDB: Using Linux native AIO 2020-08-14 15:50:23 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2020-08-14 15:50:23 0 [Note] InnoDB: Uses event mutexes 2020-08-14 15:50:23 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2020-08-14 15:50:23 0 [Note] InnoDB: Number of pools: 1 2020-08-14 15:50:23 0 [Note] InnoDB: Using SSE2 crc32 instructions 2020-08-14 15:50:23 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts) 2020-08-14 15:50:23 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M 2020-08-14 15:50:23 0 [Note] InnoDB: Completed initialization of buffer pool 2020-08-14 15:50:23 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See th e man page of setpriority(). 2020-08-14 15:50:23 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2020-08-14 15:50:23 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2020-08-14 15:50:23 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2020-08-14 15:50:23 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2020-08-14 15:50:23 0 [Note] InnoDB: 10.4.12 started; log sequence number 25563225979; transaction id 55235761 2020-08-14 15:50:23 0 [Note] InnoDB: Loading buffer pool(s) from /config/databases/ib_buffer_pool 2020-08-14 15:50:23 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-08-14 15:50:23 0 [Note] Server socket created on IP: '127.0.0.1'. 2020-08-14 15:50:23 0 [Note] Reading of all Master_info entries succeeded 2020-08-14 15:50:23 0 [Note] Added new Master_info '' to hash table 2020-08-14 15:50:23 0 [Note] /usr/sbin/mysqld: ready for connections. Version: '10.4.12-MariaDB-1:10.4.12+maria~bionic-log' socket: '/var/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distrib ution 2020-08-14 15:50:24 0 [Note] InnoDB: Buffer pool(s) load completed at 200814 15:50:24 2020-08-14 15:51:50 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown 2020-08-14 15:51:50 0 [Note] Event Scheduler: Purging the queue. 0 events 2020-08-14 15:51:50 0 [Note] InnoDB: FTS optimize thread exiting. 2020-08-14 15:51:50 0 [Note] InnoDB: Starting shutdown... 2020-08-14 15:51:50 0 [Note] InnoDB: Dumping buffer pool(s) to /config/databases/ib_buffer_pool 2020-08-14 15:51:50 0 [Note] InnoDB: Buffer pool(s) dump completed at 200814 15:51:50 2020-08-14 15:51:51 0 [Note] InnoDB: Shutdown completed; log sequence number 25563233366; transaction id 55235778 2020-08-14 15:51:51 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2020-08-14 15:51:51 0 [Note] /usr/sbin/mysqld: Shutdown complete

Thanks, @uberchuckie. My permissions on the files of interest looked good, as far as I could tell, though I went ahead and installed the dev branch to see if changing all permissions in the databases folder would help. With the dev branch installed, I get basically the same errors in the log, with an additional entry each time for Fixing file permissions. Again, reverting to 2.0.2 brings everything back to normal. I'm happy to try deleting the database itself, though I'm not exactly sure which files to delete and which to preserve. I had tried deleting a few things before my original post, but that led 2.0.2 to break as well. Thanks! Outputs of ls -l before running dev branch: drwxr-xr-x 1 nobody users 450 Aug 14 02:26 databases/ -rwxr-xr-x 1 nobody users 73728 Aug 14 02:00 aria_log.00000001* -rwxr-xr-x 1 nobody users 52 Aug 14 02:00 aria_log_control* -rw-rw---- 1 nobody users 30661 Apr 18 12:24 d5f1933a656f.err -rw-rw---- 1 nobody users 26061 Aug 14 02:00 ib_buffer_pool -rwxr-xr-x 1 nobody users 50331648 Aug 14 11:25 ib_logfile0* -rwxr-xr-x 1 nobody users 50331648 Aug 14 06:55 ib_logfile1* -rwxr-xr-x 1 nobody users 79691776 Aug 14 11:25 ibdata1* Docker log: *** Running /etc/my_init.d/10_syslog-ng.init... Aug 14 11:28:19 observium syslog-ng[12]: syslog-ng starting up; version='3.13.2' *** Running /etc/my_init.d/firstrun.sh... Using existing PHP database config file. warning: commands will be executed using /bin/sh job 1 at Fri Aug 14 11:29:00 2020 warning: commands will be executed using /bin/sh job 2 at Fri Aug 14 11:29:00 2020 *** Booting runit daemon... *** Runit started as PID 33 Database exists. Fixing file permissions. Aug 14 11:28:21 observium cron[38]: (CRON) INFO (pidfile fd = 3) Aug 14 11:28:21 observium cron[38]: (CRON) INFO (Running @reboot jobs) Starting MariaDB... 200814 11:28:24 mysqld_safe Logging to '/config/databases/observium.err'. 200814 11:28:24 mysqld_safe Starting mariadbd daemon with databases from /config/databases Database exists. Fixing file permissions. Database exists. Fixing file permissions. Starting MariaDB... ...

After updating to the latest docker I am getting nearly the same message loop as @kimocal. I don't believe this is due to database corruption, because when I revert to docker image 2.0.2 everything works. Any other ideas how to resolve? I have looked at the observium.err file and there are multiple errors related to mysql plugins and then the InnoDB file ibdata1 is deemed not writable, and then everything aborts. Thanks for any advice. Docker log: ErrorWarningSystemArrayLogin *** Running /etc/my_init.d/10_syslog-ng.init... Aug 13 17:47:15 observium syslog-ng[12]: syslog-ng starting up; version='3.13.2' *** Running /etc/my_init.d/firstrun.sh... Using existing PHP database config file. warning: commands will be executed using /bin/sh job 1 at Thu Aug 13 17:48:00 2020 warning: commands will be executed using /bin/sh job 2 at Thu Aug 13 17:48:00 2020 *** Booting runit daemon... *** Runit started as PID 33 Database exists. Starting MariaDB... Aug 13 17:47:18 observium cron[37]: (CRON) INFO (pidfile fd = 3) Aug 13 17:47:18 observium cron[37]: (CRON) INFO (Running @reboot jobs) 200813 17:47:18 mysqld_safe Logging to '/config/databases/observium.err'. 200813 17:47:18 mysqld_safe Starting mariadbd daemon with databases from /config/databases Database exists. Starting MariaDB... 200813 17:47:19 mysqld_safe Logging to '/config/databases/observium.err'. 200813 17:47:19 mysqld_safe Starting mariadbd daemon with databases from /config/databases Database exists. Starting MariaDB... ... observium.err log leading up to shutdown sequence: 2020-08-13 18:02:43 0 [ERROR] mariadbd: File '/config/databases/aria_log_control' not found (Errcode: 13 "Permission denied") 2020-08-13 18:02:43 0 [ERROR] mariadbd: Got error 'Can't open file' when trying to use aria control file '/config/databases/aria_log _control' 2020-08-13 18:02:43 0 [ERROR] Plugin 'Aria' init function returned error. 2020-08-13 18:02:43 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed. 2020-08-13 18:02:43 0 [Note] InnoDB: Using Linux native AIO 2020-08-13 18:02:43 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable 2020-08-13 18:02:43 0 [ERROR] InnoDB: The innodb_system data file 'ibdata1' must be writable 2020-08-13 18:02:43 0 [ERROR] Plugin 'InnoDB' init function returned error. 2020-08-13 18:02:43 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. 2020-08-13 18:02:43 0 [Note] Plugin 'FEEDBACK' is disabled. 2020-08-13 18:02:43 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loade d 2020-08-13 18:02:43 0 [ERROR] Failed to initialize plugins. 2020-08-13 18:02:43 0 [ERROR] Aborting

This is much later than your post from back in June. Did you figure it out? I noticed I was having this problem the other day, and eventually just added "-p 8043" into the Extra Parameters in the Advanced View of the EAPcontroller docker template. (Switch from "Basic View" to "Advanced View" in the top right of the Docker Edit screen, then scroll down to "Extra Parameters") This shouldn't be necessary given how other dockers work in unRAID, but it's an easy workaround. I do not know Docker very well, so if you came up with a better solution I'd be interested to know what it is. Note I am using 8043 as the default secure port in my EAPcontroller template. You could do something similar using port 8088 if you are using the default unsecure port, or specify both with two "-p" arguments, or use whatever ports you have specified in the template. My understanding is that with its own IP, you would not specify a port mapping such as "-p 80:8088" Hope that helps, and certainly if you've found a better solution since June, I'd be interested to hear. Thanks!

Thanks. That came about gradually, but I appreciate your suggestion and will see what happens if I shrink it back down.

Thanks again, dlandon and trurl. Diagnostics file attached. I also ran some additional tests and saw I no longer need the Plex port forward on my router, so all that's left in terms of open ports is LetsEncrypt, which points to a different IP address than the unRAID server or other dockers. Note that the LMS and Plex ports went to IP addresses that were specific to each of those dockers as well. home-raid-diagnostics-20181203-2245.zip

Thanks, both, for your replies. I looked at my router and it turns out I did have a port open for one of the LMS plugins. I went ahead and shut that down for now. I also have port forwards for a Plex docker and a LetsEncrypt docker. I will post diagnostics tonight. Thank you again.

Hey, dlandon... Not sure if this is something on your end, though from an abundance of caution I figure I should put the word out... I think my installation of your docker image got hacked. I don't know if it's in the docker files, or if it happened only to me and somehow "stuck" on my LMS docker. Here's what happened: I forced a reboot of my unraid this evening because I couldn't access LMS. Then, when I could access it again, I had a very limited number of music files visible, and saw an unknown "player" in the LMS web interface. This player had the name "ChineseProdigy Gotcha!!" At first thinking this might be a hack into my LMS from the public internet, I shut down the docker, changed the docker's IP address, and restarted. But I ended up with the same issue immediately upon restart. I then shut down the docker completely and installed snoopy86's LMS docker into a new config directory, and this did not seem to have the issue. I then deleted snoopy86's image, and reinstalled the dlandon image, using a new config directory. The new image was taking a very long time to start up, and when I looked at the log, there was a whole set of installation routines running that made me nervous, so I shut it all down. For now I'm using snoopy86, but would prefer to go back to yours if you are keeping it up to date. Note I also googled and searched the LMS forums, but couldn't find anything that included ChineseProdigy or anything reasonably similar involving LMS. Attached is a screen capture of the portion of my LMS web GUI from before I deleted the docker. It has three things that I boxed in red: the "hack" player, an "amateur repeater system" playlist that I don't recognize, and the reported total size of my music library -- the simple comparison would be that the GUI is showing 10 albums and 11 songs, vs. my actual which is around 1200 albums and 18k songs. I don't want to post my log file in a public forum, but am happy to get it to you another way, if helpful.

I'm having the same issue. miniDLNA is great, but after a certain amount of uptime, as far as I can tell the only way to stop/start it anymore is to reboot unRAID. I was about to post a simple reply to Cekodok to agree with the situation described, but I was in the middle of rebooting at the time, and now that unRAID is back I'm testing to get some logs to post -- and miniDLNA seems fine. I'll post again in a couple of days, with log data...

Wow! Update worked for me, too. I guess I should have spoken up months ago. Thank you!!

@S80_UK, I am having almost the exact same problem as you, with a few differences: - I am trying to connect with my iPhone 6 running iOS 10.2 -- more current hw/sw than the Soundbridge (mine died in 2009...) - I have also tried to connect using the latest iTunes on Windows 10, and the same thing happens - I do not even get the "Failed to set ownership on logfile" error that you are showing. My log simply goes from the "scan completed" line to the "taking off" line when I connect I believe there used to be two versions of the daapd Docker for unRAID, but one stopped being maintained. I had been using the other version successfully, but started having problems when I switched to the LinuxServer.IO version. I believe I have deleted all legacy data from the previous docker, and have tried deleting / reinstalling this version a few times. I come back to this every few weeks in hope an update to the Docker will fix the problem for me I don't see anything obvious in the logs that would suggest daapd is crashing, even with log level set to Debug. But clearly it is crashing and restarting repeatedly as my phone tries to reconnect each time it comes back up. If helpful my docker command line is: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="daapd" --net="host" --privileged="true" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -v "/mnt/user/Music":"/music":ro -v "/mnt/cache/appdata/daapd":"/config":rw linuxserver/daapd 797e19daba2f6c1977680451e14afd43f55a0826be1d860d370cd5c33880c940 Would love suggestions from the community on how to resolve this. Thanks! ps - @S80_UK, if you are testing things at all, I have found that by disabling scan at startup in the config file, you can avoid the long wait for your library to rescan every time daapd restarts. Somewhat helpful for testing.

I'm having the same issue. Kind of a bummer. Maybe this will be my excuse to migrate to Nextcloud In my case, I am sure part of the issue is that I was updating Owncloud from within its own web UI, and when the Docker updated within unRAID it didn't pull in the latest version of Owncloud, which I guess I would have expected (my updates had taken me to 9.0.4.1) I had some other issues I was able to fix from the docker command line about a year ago, so I might try messing around there first. If I come up with a solution I will post back here.

In case anyone else lands here...Symform is being discontinued: https://community.symform.com/entries/99963588-Symform-service-to-be-discontinued-on-July-31-2016

I will echo the comments of people who are unable to upgrade past ownCloud 8.2.2. I have reviewed the ownCloud admin manual and tried to follow the instructions posted on this forum, have set EDGE=1 in my advanced settings, but have not had any luck getting 9.0 installed. The following are unclear to me: 1. If I am going to delete my ownCloud installation other than the data and config folders, what are the paths to the relevant directories, or what is the process? It seems like if I just remove the docker container (+/- the image) from the Docker tab in the unRAID gui, I still can't execute the upgrade. Though maybe I'm missing a step. If I try to remove everything manually, I can't tell what directories to remove because the docker files seem to be living in several directories with very long pathnames, including some subfolders of an nginx path. 2. The ownCloud administration manual talks about using apt to update packages, but I am confident (99%?) that's not the way forward for an unRAID docker container, so the guidance to read the ownCloud manual doesn't seem to be helpful. Though again maybe I'm missing something. 3. Is gfjardim's docker container actually updated for 9.0 yet? Does this matter? I am thinking the answers are "no" and "yes" -- in that order -- given my experience to-date. Still, since other people seem to be able to upgrade to 9.0 it would be helpful just to have clarity on this point. Thanks!