jwmoss
-
Posts
7 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by 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.
-
1 minute ago, jwmoss said:
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
****
This was 2 hours prior:
Jul 24 19:46:05 Tower kernel: TCP: br0: Driver has suspect GRO implementation, TCP performance may be compromised.
-
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
****
-
Issue in title. See attached for anonymized logs.
-
Here's a fresh copy. The error just happened once again.
-
When attempting to browse to /mnt/user, I get the error here:
/bin/ls: cannot access 'user': Transport endpoint is not connectedI'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!
Server becomes unresponsive over network
in General Support
Posted
Uploading the syslog file after the latest unresponsiveness + new support bundle.
syslog tower-diagnostics-20230419-0828.zip