The browser just hangs and the settings never get changed after clicking Apply. Browser says "Waiting for ...." in status bar.

 

(Possibly related: the page never refreshes after creating shares, you just have to close it out but the share is created.)

 

log says:

Apr 28 12:21:33 fs emhttpd: Starting services...

Apr 28 12:24:33 fs nginx: 2021/04/28 12:24:33 [error] 4045#4045: *5719652 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.21, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "fs", referrer: "http://fs/Shares/Share?name="

 

(seems nginx has crashed again as can't user userscripts any more either, is there a good way to restart it?)

Edited April 28, 20215 yr by cinereus

We'll need your diagnostics. If you can get to Tools -> Diagnostics, download them from there and then attach the entire zip to your next post in this thread.

 

If you can't get them from the webgui, you can use SSH or the local console.  Log in, then type

diagnostics

The diagnostics will get saved onto the flash drive (logs folder).

Shut down the server by typing:

powerdown

pull the flash and post the entire zip file to your next post in this thread

Seems to have resolved itself 24 hours later. I think ngnix managed to restart itself. Is there a way to force this manually?

Without diagnostics this is just speculation, but it is unlikely that nginx restarted itself.

 

To answer your question, this is how you restart nginx:

  /etc/rc.d/rc.nginx restart

Note that this is not a common troubleshooting step

6 hours ago, ljm42 said:

Without diagnostics this is just speculation, but it is unlikely that nginx restarted itself.

 

To answer your question, this is how you restart nginx:

  /etc/rc.d/rc.nginx restart

Note that this is not a common troubleshooting step

Here's diagnostics:

fs-diagnostics-20210430-1022.zip

 

Not going to be related, but your network goes down and up a fair amount.  Maybe replace the cable or use a different port on the switch?

47 minutes ago, Squid said:

Not going to be related, but your network goes down and up a fair amount.  Maybe replace the cable or use a different port on the switch?

Please can you show me where you see that in the logs?

Apr 30 10:06:28 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
Apr 30 10:06:32 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX
Apr 30 10:06:33 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
Apr 30 10:06:36 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX

Apr 29 11:37:03 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
Apr 29 11:37:07 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX
Apr 29 11:37:08 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
Apr 29 11:37:11 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX
Apr 29 11:37:14 fs login[7961]: ROOT LOGIN  on '/dev/pts/1'

Apr 28 16:59:17 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
Apr 28 16:59:19 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX

Apr 28 10:39:54 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
Apr 28 10:39:58 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX
Apr 28 10:39:59 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
Apr 28 10:40:02 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 1 Gbps, Flow Control: RX/TX

Apr 27 23:34:26 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Down
Apr 27 23:34:29 fs kernel: ixgbe 0000:05:00.1 eth1: NIC Link is Up 100 Mbps, Flow Control: RX/TX

 

I think that's just a direct connection to a PC that is being put to sleep. Main network is on eth0.

Edited April 30, 20215 yr by cinereus

I'm still having this issue updating share settings. It just seems to hang indefinitely:

 

May  2 13:26:23 fs emhttpd: error: send_file, 151: Broken pipe (32): sendfile: /usr/local/emhttp/update.htm
May  2 13:26:23 fs emhttpd: error: send_file, 151: Broken pipe (32): sendfile: /usr/local/emhttp/update.htm
May  2 13:26:23 fs emhttpd: error: send_file, 151: Broken pipe (32): sendfile: /usr/local/emhttp/update.htm
May  2 13:26:23 fs emhttpd: error: send_file, 151: Broken pipe (32): sendfile: /usr/local/emhttp/update.htm
May  2 13:26:23 fs emhttpd: error: send_file, 151: Broken pipe (32): sendfile: /usr/local/emhttp/update.htm
May  2 13:26:23 fs emhttpd: Starting services...
May  2 13:27:41 fs nginx: 2021/05/02 13:27:41 [error] 13965#13965: *7101174 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.21, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket/update.htm", host: "fs", referrer: "http://fs/Shares/Share?name=downloads"
May  2 13:28:05 fs nginx: 2021/05/02 13:28:05 [error] 13965#13965: *7101443 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.21, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket/update.htm", host: "fs", referrer: "http://fs/Shares/Share?name=droppy"
May  2 13:28:26 fs nginx: 2021/05/02 13:28:26 [error] 13965#13965: *7101704 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.0.21, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket/update.htm", host: "fs", referrer: "http://fs/Shares/Share?name=files"
May  2 13:29:23 fs nginx: 2021/05/02 13:29:23 [error] 13965#13965: *7100751 upstream timed out (110: Connection timed out) while reading upstream, client: 192.168.0.21, server: , request: "POST /update.htm HTTP/1.1", upstream: "http://unix:/var/run/emhttpd.socket:/update.htm", host: "fs", referrer: "http://fs/Shares/Share?name=video"

 

Edited May 2, 20215 yr by cinereus