delaney

+1 here as well

Symptoms are very similar to what I was seeing - when I looked at my log output (from the openeats app docker container) - I could see for some reasons, that the the application (I labeled mine openeats-app) was trying to connect to the openeats-app as the database server. (I have created a seperate mariadb docker container called openeats-mariadb). I assume somewhere along the way of environment variables, templates, shell scripts etc. the wrong hostname was being picked up / replaced along the way. I spent a little time trying to troubleshoot - to the point that within the container I was running the schema commands from /code/base/migrate.py pythong file and was getting the same errors - database connection errors. Which make sense given it was trying to connect to the app container. (for the record, after having shelled into the app container, the command I was running as an example was "python /code/base/migrate.py reset_db") In the end I gave up and just ran the container with MYSQL_USER set to root - as soon as I did that, the app ran as expected. Happy to share more info, but thought I would include the above in case it helps anyone get started, or for anyone wanting to do more in-depth troubleshooting. (My gut feel is that the errors is in environment variables - the out put from the shell 'set' command differed from the output of 'env' - mainly in differences between / missing database related vars - I just ran out of time/patience trying to track this down) (As always, thank you to the maintainer for putting the work together for the rest of us to use)

Awesome, thank you

Thanks for logging an issue @moppen - I jumped on to have a look at the issue to see if I can help provide some details for troubleshooting. https://github.com/linuxserver/docker-booksonic/issues/25 has been raised for this issue so keeping an eye on that one for updates looks like the go. You can close the one you raised as a duplicate I think. Kind regards, Del

Good morning, FWIW same error in container log with :latest tag, although a different result for me when browsing to the default page. Possibly not related, but poking around to see if anyone had detail on error cause/fix for latest, I see that the version tag for the :latest version looks unusual: image null-ls76 When diving in to the tag line 22 from the image history reads |4 BOOKSONIC_RELEASE=null BUILD_DATE=2020-08-06T..... Mentioning in case it provides a clue - possibly with the underlying build/package process that grabs the booksonic app itself. As always, thanks for the awesome work LSIO team. Kind regards, Del

Hi UNRAIDer's, I've not had a reoccurrence of the symptoms described in the original post since the BIOS updated documented in the second post, so I am calling this one solved.

Logging an update in case internet searches brings anyone else with the same problem here..... My MOBO / CPU combination is: Mobo : ASUSTeK COMPUTER INC. - ROG MAXIMUS XI HERO CPU : Intel® Core™ i7-8700K CPU @ 3.70GHz I was running an older BIOS - the board shipped with American Megatrends Inc. Version 1502. Dated: 02/21/2020. This morning I upgraded the BIOS to: American Megatrends Inc. Version 1502. Dated: 02/21/2020 So far uptime is approaching 6 hours, given that the crashes occurred a couple of days apart, I will continue to monitor, if I see no similar crashes/lock-ups after a week will report back here. (update)

Hi UNRAIDer's, As always, thanks heaps in advance for any insight you can share on troubleshooting my MCE's I am posting this also in case this information is helpful for the great work occurring in the 6.9 release space. I've attached my diagnostics from my primary UNRAID server which has rebooted once, and locked up once this week with MCE's. I don't have the details from the first event - I put it down to the "that's weird. oh well stuff goes sideways sometimes if running for long enough" and kept going. So the attached diagnostics are from the second event. Key points that I *think* are helpful: - Earlier in the week (~ 7 days ago) - I upgraded both my primary and secondary UNRAID servers to 6.9 Beta 22. - To date - no issues with the secondary server (running different hardware) - but also under a different load / usage profile - both MCE events occurred after the move to 6.9 Beta 22 - both machines have been running UNRAID in different configurations for years - undergoing incremental hardware upgrades along the way. - This morning I ran a memtest for ~4 3/4 hours on the affected machine with no errors detected. - I do have some services that are cyclical/self referencing (my syslog server, pfsense e.g.) so there are some errors in the startup sequence about being unable to contact these services - these are "expected" - at least have been to date. - I do have some BIOS updates available for the mobo running in this install which I intend to apply - I note some references to CPU bugs being detected in the logs - will post a follow up here should the BIOS updates be effective but that will take at least a few days. (Thanks to - Is it fixed? or has it just not occurred again yet?) I've inserted a snippet from the syslog that I think is most pertinent - full log contained in the diagnostics attached. Not that I think it matters - all times are UTC+10 Kind regards, Del ... ... ... Jul 10 12:04:21 vision kernel: virbr0: port 1(virbr0-nic) entered disabled state Jul 10 12:04:21 vision kernel: L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. ... ... ... Jul 10 12:25:49 vision root: Fix Common Problems: Error: Machine Check Events detected on your server Jul 10 12:25:49 vision root: Hardware event. This is not a software error. Jul 10 12:25:49 vision root: MCE 0 Jul 10 12:25:49 vision root: CPU 3 BANK 0 TSC 33255d618d8 Jul 10 12:25:49 vision root: ADDR 1ffff815fbcc4 Jul 10 12:25:49 vision root: TIME 1594346856 Fri Jul 10 12:07:36 2020 Jul 10 12:25:49 vision root: MCG status: Jul 10 12:25:49 vision root: MCi status: Jul 10 12:25:49 vision root: Corrected error Jul 10 12:25:49 vision root: Error enabled Jul 10 12:25:49 vision root: MCi_ADDR register valid Jul 10 12:25:49 vision root: MCA: Instruction CACHE Level-0 Instruction-Fetch Error Jul 10 12:25:49 vision root: STATUS 9400004000040150 MCGSTATUS 0 Jul 10 12:25:49 vision root: MCGCAP c0c APICID 6 SOCKETID 0 Jul 10 12:25:49 vision root: MICROCODE d6 Jul 10 12:25:49 vision root: CPUID Vendor Intel Family 6 Model 158 ... ... ... vision-diagnostics-20200710-1236.zip

Yikes

Thanks for the heads up JohnM - haven't accumulated enough disks to require expansion cards yet but it is not far away and has always been the plan When you say issues - just curious - do mean getting the LSI cards recognised, or do you mean stability / performance issues during operation? @dikkiedirk - Not specifically as part of this conversation (is that what you meant?) - I've just been keeping an eye out for announcements. Apart from a small problem with using unRAID to mount other samba shares (so I can put files on the array - /user/sbin/mount.cifs is missing; I saw I a post from limetech that makes me think it is fixed in the next beta / release) 5b14 has been rock solid in my (limited) experience.

and if anyone was still playing along at home - everything just worked out of the box (FWIW I have been using a Lexar Firefly 4Gb - went to set up a backup today using a Kingston data traveller (DT101 G2) and no matter what I did - including a mobo bios upgrade, could not get the kingston to boot.)

Just in case anyone was playing along @ home, grabbed these parts today, system assembled and unRAID 5b14 up and running with no problems at all. Just zeroing disks, and setting up parity drive at the moment - will start transfer tests when done. I'll report back just in case anyone was interested in the result.

Thanks Raj - turns out it was a V2 - all parts acquired, let the assembly begin, then b14 it is

Thanks for coming back so quickly Raj. Local suppliers have a CX500 but until I can call them today wasn't sure if it was a V2 or not - maybe it doesn't matter too much, but it was only a $10 jump to the CX600 so I wasn't concerned about that. I forgot to mention that I was planning on throwing an Intel based NIC in and running 4.7 - but I have people talking about b14 being stable, and if the stable 5.0 comes out in a couple of days (potentially) I don't think I'd bother. Kind regards, Delaney

Thanks Raj - email on it's way