Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Server web UI becoming non-responsive multiple times a day (until powercycle)

Featured Replies

I'm seeing a significant issue with my server where the webui is becoming non-responsive multiple times a day, until I reboot, it often happens AFTER login loads. I have no idea what's causing it after 5-10 minutes I get 500 INTERNAL SERVER ERROR.

Could someone help me understand how to troubleshoot? I'm attaching the log I got

 

 

zeus-diagnostics-20221123-1230.zip

Solved by JorgeB

  • Author
12 minutes ago, JorgeB said:

Enable the syslog server and post that after the next crash.

thanks, enabled it, will post it when it becomes unresponsive. 

  • Author
On 11/23/2022 at 12:55 PM, JorgeB said:

Enable the syslog server and post that after the next crash.

So, I enabled it, but my understanding is that it won't copy the syslog information until the reboot.  if I'm having to do power cycle, I don't think syslog gets kept. 

am I misunderstanding? I couldn't access GUID this morning, so I resetted it via case's reset button, but now I can't find syslog anywhere... 

16 minutes ago, takkkkkkk said:

am I misunderstanding?

Yes, it should copy the syslog in real time.

  • Author
24 minutes ago, ChatNoir said:

Yes, it should copy the syslog in real time.

Thank you! I just exported the entire USB, and was able to access the flash, and see syslog.

below is the syslog I got, was trying to read through, could not decipher what has caused the GUI to go offline overnight...

 

 

syslog

  • Author
On 11/23/2022 at 12:55 PM, JorgeB said:

Enable the syslog server and post that after the next crash.

Just realized I was able to capture as it went down it seems like below is what's causing the crash, but not really what what's happening...

 

Nov 24 16:28:22 ZEUS nginx: 2022/11/24 16:28:22 [error] 7739#7739: *208046 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.42, server: , request: "GET /webGui/styles/default-fonts.css?v=1663520428 HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:28:22 ZEUS nginx: 2022/11/24 16:28:22 [error] 7739#7739: *208046 auth request unexpected status: 504 while sending to client, client: 192.168.1.42, server: , request: "GET /webGui/styles/default-fonts.css?v=1663520428 HTTP/2.0", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:28:22 ZEUS nginx: 2022/11/24 16:28:22 [error] 7739#7739: *208046 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.42, server: , request: "GET /webGui/styles/default-cases.css?v=1663520363 HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:28:22 ZEUS nginx: 2022/11/24 16:28:22 [error] 7739#7739: *208046 auth request unexpected status: 504 while sending to client, client: 192.168.1.42, server: , request: "GET /webGui/styles/default-cases.css?v=1663520363 HTTP/2.0", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:28:22 ZEUS nginx: 2022/11/24 16:28:22 [error] 7739#7739: *208046 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.42, server: , request: "GET /webGui/styles/font-awesome.css?v=1663520455 HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:28:22 ZEUS nginx: 2022/11/24 16:28:22 [error] 7739#7739: *208046 auth request unexpected status: 504 while sending to client, client: 192.168.1.42, server: , request: "GET /webGui/styles/font-awesome.css?v=1663520455 HTTP/2.0", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:39:02 ZEUS nginx: 2022/11/24 16:39:02 [error] 7739#7739: *208046 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.42, server: , request: "GET /webGui/styles/context.standalone.css?v=1640104829 HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:39:02 ZEUS nginx: 2022/11/24 16:39:02 [error] 7739#7739: *208046 auth request unexpected status: 504 while sending to client, client: 192.168.1.42, server: , request: "GET /webGui/styles/context.standalone.css?v=1640104829 HTTP/2.0", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:39:02 ZEUS nginx: 2022/11/24 16:39:02 [error] 7739#7739: *208046 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.42, server: , request: "GET /webGui/styles/jquery.sweetalert.css?v=1657742116 HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:39:02 ZEUS nginx: 2022/11/24 16:39:02 [error] 7739#7739: *208046 auth request unexpected status: 504 while sending to client, client: 192.168.1.42, server: , request: "GET /webGui/styles/jquery.sweetalert.css?v=1657742116 HTTP/2.0", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:39:03 ZEUS nginx: 2022/11/24 16:39:03 [error] 7739#7739: *208046 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.42, server: , request: "GET /webGui/styles/default-black.css?v=1651160982 HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:39:03 ZEUS nginx: 2022/11/24 16:39:03 [error] 7739#7739: *208046 auth request unexpected status: 504 while sending to client, client: 192.168.1.42, server: , request: "GET /webGui/styles/default-black.css?v=1651160982 HTTP/2.0", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:49:42 ZEUS nginx: 2022/11/24 16:49:42 [error] 7739#7739: *208046 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.1.42, server: , request: "GET /webGui/styles/dynamix-black.css?v=1648920316 HTTP/2.0", subrequest: "/auth-request.php", upstream: "fastcgi://unix:/var/run/php5-fpm.sock", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 16:49:42 ZEUS nginx: 2022/11/24 16:49:42 [error] 7739#7739: *208046 auth request unexpected status: 504 while sending to client, client: 192.168.1.42, server: , request: "GET /webGui/styles/dynamix-black.css?v=1648920316 HTTP/2.0", host: "192.168.1.99", referrer: "https://192.168.1.99/Dashboard"
Nov 24 17:00:01 ZEUS kernel: mdcmd (54): set md_write_method 1
Nov 24 17:00:01 ZEUS kernel: 
Nov 24 17:01:49 ZEUS  emhttpd: spinning down /dev/sdg
Nov 24 17:08:11 ZEUS  emhttpd: spinning down /dev/sdn

 

syslog

  • Community Expert
  • Solution

Looks like this isse:

 

 

  • Author
16 hours ago, JorgeB said:

Looks like this isse:

 

 

THANK YOU!! have downgraded all my torrent dockers, will wait and see

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.