January 16, 20188 yr Good day Crew, The server has been updated to 6.4 stable and running for 3 days now. Fix Common Problems just alerted me to an issue that I have never seen before: Call Traces found on your Server Diagnostics are attached. Any advice would be greatly appreciated! tower-diagnostics-20180116-1634.zip
January 16, 20188 yr Someone posted same error over on redhat bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1529971 Does everything seem to still work?
January 17, 20188 yr Well it's not a segfault (kernel crash), it's a warning that something happened that "shouldn't" happen, along with a stack dump to aide developer.
January 27, 20188 yr Hi, I've also seen the call traces since upgrading to v6.4.0 Everything was ok for a few days, but then I had a full lock-up of my system. After this I ran 2 full parity checks that both found errors, in between I removed plug-ins which I thought could have caused the issues, namely Pre-Clear which I'd seen could cause issues with 6.4. I then to rolled back the docker changes and network bridge, and another full parity check showed zero errors. Everything seems to be back to normal, after keeping an eye on logs for a few days. And I plan on running another one after the weekend for good measure. In hindsight I should have been more diligent in saving logs/diagnostics, but I did start saving copies after something seemed to be really out of the ordinary. They're attached just incase they can assist with troubleshooting. And I can provide more details/context of what I saw/did to get to this point. Edited February 17, 20188 yr by Tyler
Archived
This topic is now archived and is closed to further replies.