June 2, 20233 yr I keep having issues so hopefully you all can help! At this point I have pretty regular issues when doing a backup. I set it to happen in the middle of the night. I also have a user script set (for the following night) to backup my nextcloud data offsite. I can't get through 1 week without one of these two nights bringing down my server in some way. Either the whole thing freezes up and I have to hard reset it or docker refuses to start and I have to reboot the whole thing. The attached diagnostic is from an instance when docker wouldn't start. I get a message when trying to start up the docker service again via the web interface: Quote **Warning**: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in **/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php** on line **712** Couldn't create socket: [111] Connection refused **Warning**: Invalid argument supplied for foreach() in **/usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php** on line **898** Following another post here, I decided to delete my docker.img file. Perhaps it is corrupt. But I can't! Even trying to change the name of the file on the command line gives me an error about a read-only file system. Can anyone see in the diagnostics what's going on? A possible clue - This seemed to start happening after I set the server to be a syslog server and I used it's own address as the remote (I did this to try and debug the freezing issue). Thanks in advance! tower-diagnostics-20230602-0450.zip
June 2, 20233 yr Community Expert Cache filesystem went read-only, with an error that usually indicates RAM issues, start by running memtest.
June 2, 20233 yr Author It's pretty new memory - only a few months old. I'm running a memtest now but I'm a few hours in already with no issues.
June 3, 20233 yr Author 9.5 hours with 4 passes and no errors. Can you explain any more why that make you think memory is bad?
June 3, 20233 yr Community Expert 1 hour ago, belowe said: Can you explain any more why that make you think memory is bad? 19 hours ago, JorgeB said: with an error that usually indicates RAM issues Reboot and post new diags after array start.
June 4, 20233 yr Community Expert Everything look good for now, post new diags if you run into issues again.
June 7, 20233 yr Author Hit issues again. This time after CA Backup ran. Although my docker services were up, things weren't right. Home assistant had some entities disconnected and couldn't ping google for connectivity check. All docker container versions were not available and the UI was generally slow. So I decided to try and restart docker. I disabled it in settings and suddenly the syslog started spewing SMB2 failure messages. I restarted docker and though everything started, it all looked the same with the container versions etc. SMB messages were still spewing. So I pulled diags and restarted. tower-diagnostics-20230607-0348.zip
June 7, 20233 yr Author Oh an apparently I'm still spewing bad SMB2 messages. Here are diagnostics after the reboot and disabling docker. tower-diagnostics-20230607-0400.zip
June 7, 20233 yr Community Expert Jun 7 03:45:32 Tower avahi-daemon[5227]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** And once the docker service was stopped all the SMB messages started: Jun 7 03:45:32 Tower emhttpd: shcmd (872305): /etc/rc.d/rc.docker stop Jun 7 03:45:33 Tower smbd[5573]: [2023/06/07 03:45:33.308920, 0] ../../libcli/smb/smb2_signing.c:722(smb2_signing_check_pdu) Jun 7 03:45:33 Tower smbd[5573]: Bad SMB2 (sign_algo_id=1) signature for message So try to find if it's a container doing that.
June 7, 20233 yr Author If I stop the array disable docker and disable SMB, the messages stop. As soon as I enable SMB again, they start again (even with docker stopped). Should I try another combination of actions?
June 7, 20233 yr Author Yep. I can still get to shares via a fstab cifs mount though. I also deleted and recreated my docker vdisk for sanity. This feels like I have multiple things at play here. Thanks for the help.
June 8, 20233 yr Author Unmounting and re-mounting all cifs shares (on machines accessing my server) seems to fix the log spewing problem. Back to the original issue...? I'll keep you posted. Thanks
June 24, 20233 yr Author So the thing died again today. Differently than before, this was NOT during a backup or anything. The last entry in the syslog before the failure was 'Jun 23 11:43:05 Tower emhttpd: read SMART /dev/sdb' Diagnostics from my reboot a couple of hours ago are attached. I'm sort of at a loss here. I also don't know if I should update to the newest release or should try to nail this issue down first. Thoughts? tower-diagnostics-20230623-1727.zip
June 24, 20233 yr Community Expert Syslog starts over after rebooting and if there wasn't anything logged on the persistent log not much to go on, but it usually points to a hardware issue.
August 7, 20232 yr Author Solution Finally got all of this solved. Seemed to stem from mavclan in docker. Switched to ipvlan and things are magically fixed.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.