Jump to content

balsman225

Members
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

0 Neutral

About balsman225

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  1. Thanks for the quick reply. I’ve been sticking to 6.5.3 as it been the most stable with my static IP’ed Plex docker but I know I’m going to have to update eventually. I’ll look into creating a VLAN for the dockers and give that a shot when 6.8.0 goes stable.
  2. Out of curiosity have you tested this issue on any newer releases (6.8.0)?
  3. Moved all docker traffic to a dedicated interface (br2) - leaving br0 (bond of eth0 and eth1) for other traffic. I was hoping this could alleviate the potential problems with the macvlan issue with br0 and static IPed containers. But I had another crash today. I formatted my flash and I’m going back to 6.5.3 for now since I know my setup will work fine with that.
  4. Doing some digging in the forums and my issue may be similar to this one - The strange part is that user Hoopster stated they see this issue with macvlan all the way back to 6.5.0 My server was running perfectly fine on 6.5.3 with the same setup.
  5. Another Crash today - Here is what was displayed on the Console. Also attaching the syslog from the flash drive. Around 4:26PM Central time is when I got the notification from uptime robot that is was down. in the syslog around "Jun 1 16:41:10" would have been when the server was rebooted. Any help would be approached to see what is causing this. I think Im going to roll back to 6.5.3 if the issue isn't something obvious. Thanks! syslog
  6. Hello all - I Need some assistance. My server runs great on 6.5.3 - runs months without issues. When I try to upgrade to 6.6.7, or the last attempt 6.7, my server will crash after a few days. My most recent attempt was on Tues. - I backed up my flash drive, formatted it, used the USB creator to install 6.7 and then restored my config folder. Booted up the server and ran fine until today. GUI, network and shared were all unresponsive. I was able to get to the local console and copy the syslog but could not get a diagnostic bundle (just hung at “Starting diagnostics collection”). I rebooting the server and its currently running a parity check, I collected a diag just even though it would have been better before the reboot. I also ran a memtest for 24 hours without any errors so don't think its a hardware issue since it had been running fine on 6.5.3. I’m a bit at a loss what is causing the issues with the server post 6.5.3 - any guidance would be appreciated. cargo-diagnostics-20190531-0041.zip syslog-2019.txt