0x0x0x

Members
  • Posts

    20
  • Joined

  • Last visited

Everything posted by 0x0x0x

  1. Changed Status to Closed Changed Priority to Minor
  2. After erasing my flash drive and re-installing I am now, once again, stable.
  3. Alright, Thanks for your dedication to helping me fix these issues. I have the server running (for now) in safe mode. I will give it some time before re-enabling docker and VMs.
  4. Changed Status to Open Changed Priority to Urgent
  5. Here is the latest syslog after the latest crash. syslog
  6. I'm not sure what's happening then. In my Docker settings I have it set to ipvlan?
  7. Sure, here is the output of the syslog from the USB drive. syslog
  8. Hello, I've been trying for days to upgrade to 6.12.x and the server does upgrade without any issues. However, I have a seemingly random timeframe before it locks up and does not ever respond to pings again. I have to powercycle it to get it running again. Please see the attached diagnostics, I am desperate to get these issues resolved. tower-diagnostics-20240117_0548.zip
  9. After spending a couple of days to test things I am still having instability issues even after going through the linked release notes and disabling or changing settings in the recommended fashion. I can no longer access the Community Applications. I have Intel drivers for my NICs not realtek. I do have a realtek device that's an SDR for Piaware. I am unsure how to proceed and would genuinely welcome some advice on returning to a stable platform. Thanks for all your help friends.
  10. I am having issues with stability since updating to 6.12.6. After roughly 20 minutes of uptime the entire server goes down and doesn't even respond to pings. Attached please find my diagnostics. tower-diagnostics-20240105-1732.zip
  11. Hello again, Here is the syslog from my system. I tried a new cable but the behavior persisted so I just removed the drive from the machine for the time being. syslog
  12. I have enabled the write to flash option within the syslog server. Here are the diagnostics. tower-diagnostics-20230605-1216.zip
  13. Alright, I'll try that and report back.
  14. I haven't been able to ping it or have SSH respond.
  15. Hello, I recently upgraded to this release. After about 1 hour of use the web gui becomes inaccessible and the server quits responding to ping. I cannot provide diagnostics since I can't access it. What details would be most helpful for troubleshooting?
  16. There seems to be no way to re-enable the previous layout of CA? Is there a setting of sort I am completely missing the 'forest because of the trees' over?
  17. I'm seeing roughly the same output in my logs as the previous user. I attempted to start the container and it appears to start fine according to the logs. I open the webgui and all I see is a black screen and off towards the left hand side of my monitor I have a small arrow icon that doesn't seem to do anything when clicked. I skimmed the logs and there is mention of a couple of deprecated items related to GUAC user and password. I removed those from my container and tried to start again. I am now able to start the container, I see the calibre GUI and it seems to work alright for a short time. After ~2-3 minutes of idle, the container appears to disconnect from the VNC session. I don't seem to find any additional environment variables that I can attempt that will lengthen the time frame before the session disconnects and stops working. Any recommendations @linuxserver.io?
  18. Hello, I'm pulling from the latest tag and this is the message I am seeing with the webui: 400 Bad Request Illegal key 'lightstep_guid/lite-web' Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/cherrypy/_cprequest.py", line 734, in process_headers self.cookie.load(value) File "/usr/lib/python3.9/http/cookies.py", line 532, in load self.__parse_string(rawdata) File "/usr/lib/python3.9/http/cookies.py", line 596, in __parse_string self.__set(key, rval, cval) File "/usr/lib/python3.9/http/cookies.py", line 488, in __set M.set(key, real_value, coded_value) File "/usr/lib/python3.9/http/cookies.py", line 353, in set raise CookieError('Illegal key %r' % (key,)) http.cookies.CookieError: Illegal key 'lightstep_guid/lite-web' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/site-packages/cherrypy/_cprequest.py", line 638, in respond self._do_respond(path_info) File "/usr/lib/python3.9/site-packages/cherrypy/_cprequest.py", line 666, in _do_respond self.process_headers() File "/usr/lib/python3.9/site-packages/cherrypy/_cprequest.py", line 736, in process_headers raise cherrypy.HTTPError(400, str(exc)) cherrypy._cperror.HTTPError: (400, "Illegal key 'lightstep_guid/lite-web'") Powered by CherryPy 18.6.0 Any steps I can take to alleviate this error? I was able to fix the issue I was having. If you find this in the future, I used a Firefox extension "Cookie Quick Manager". (I also use the "Temporary Containers" and "Multi-Account Containers" extensions. I have all my unraid docker containers open in the same tab/category each time.) Using Cookie Quick Manager, I had to delete cookies that contained "lightstep_guid" and "lite-web".