jwmoss

Members
 View Profile  See their activity

  • Posts

    7

  • Joined

  • Last visited

 Content Type 

Everything posted by jwmoss

  1. jwmoss
    Uploading the syslog file after the latest unresponsiveness + new support bundle. syslog tower-diagnostics-20230419-0828.zip
  2. jwmoss
    Server continues to stay online, despite network connectivity being lost. I have br0, host, and proxynet network interfaces. Docker is using ipvlan. I don't see any signs of memory corruption. tower-diagnostics-20230418-1631.zip
  3. jwmoss
    This was 2 hours prior: Jul 24 19:46:05 Tower kernel: TCP: br0: Driver has suspect GRO implementation, TCP performance may be compromised.
  4. jwmoss
    Uploaded persistent logs. This wasn't during a parity check, which leads me to believe some sort of hardware failure. Not sure where to start? First line of problem: Jul 24 21:10:32 Tower kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12 **** syslog
  5. jwmoss
    Issue in title. See attached for anonymized logs. tower-diagnostics-20220703-1821.zip
  6. jwmoss
    Here's a fresh copy. The error just happened once again. tower-diagnostics-20210210-1402.zip
  7. jwmoss
    When attempting to browse to /mnt/user, I get the error here: /bin/ls: cannot access 'user': Transport endpoint is not connected I've seen this behavior before with rclone (which I was mounting a share inside of there) and I believe what may have caused this. Here's what I've done to eliminate this: 1. Remove all rclone mount scripts that are trying to mount into /mnt/user 2. Remove rclone plugin(s). I'm still having the issue. Help! tower-diagnostics-20210210-1349.zip