January 16, 20233 yr Hi, I'm preparing to upgrade to 6.11.5, but I have some weird issues with my server that I'd like to try and sort out before I do. I've had the issues for a while, and I think they started after the log went full and strange things started happening. The GUI was unresponsive, the Docker page didn't work, Settings page didn't work, VM page didn't work - but all the Docker Containers worked and all the VMs worked. I decided to manually delete system.log.1 from the system to free up space, only to realize it was stored in ram and it didn't really matter at all, but at least the WebUI became a bit more responsive. I then rebooted the server after a while when I had time to deal with any issues on boot, but to my surprise there were none. After a while I noticed that I no longer had the choice of "Custom : br0" as a network in my Docker settings, which means I no longer can assign static IP addresses with my local network range. I also can't collect diagnostics from the WebUI, but I was able to do so via the command line. Is this a sign of a dying flash drive, or is something else afoot? Diagnostics attached. aram-diagnostics-20230115-1940.zip Edited March 8, 20233 yr by reverend remiel
January 23, 20233 yr Author Noone? Anyone? Is more information required? If so, please tell me what you need and I'll do my best to provide it.
January 23, 20233 yr If you stop the array and go into settings network down the bottom you can add in a static ip and select br0 from the dropdown. as for ram filling with syslog this can happen rebooting is a fix to clear it but you need to findout what is logging to syslog so much
March 8, 20233 yr Author I figured this one out as well, with help from other posts on the forum. The culprit was that "Enable bonding" was, well, enabled. As I replaced a disk last night and everything else has been down most of the day, I figured I'd look into the network settings again based on posts I found when searching. Disabling bonding solved the issue - I now have the option to use "Custom: br0" as a docker container network and can thus once again assign static IP addresses to docker containers.
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.