WebUI stops working after about 30 minutes

[Don Intellys]

Not sure if someone has already answered this, but here is my situation. I installed this new install FreeNAS-9.10.2-U5 on a SuperMicro with dual Intel Xeon E5-2620, 128 GB RAM and a lot of disk space. I have it configured as a FibreChannel target (works flawlessly, thanks to the tunables listed in the forums). Everything works great except, if I don't stay active on the WebUI, after about 30 minutes or so, I can no longer get into the WebUI or SSH. I have to walk up to the device and restart the django and nginx services. I wait about 5 minutes and then I can get into the UI again.

Anyone have this problem?

 

[Spearfoot]

Not sure if someone has already answered this, but here is my situation. I installed this new install FreeNAS-9.10.2-U5 on a SuperMicro with dual Intel Xeon E5-2620, 128 GB RAM and a lot of disk space. I have it configured as a FibreChannel target (works flawlessly, thanks to the tunables listed in the forums). Everything works great except, if I don't stay active on the WebUI, after about 30 minutes or so, I can no longer get into the WebUI or SSH. I have to walk up to the device and restart the django and nginx services. I wait about 5 minutes and then I can get into the UI again.

Anyone have this problem?

Yikes!

Please post your full system specifications, per the Forum rules.

Have you examined the system logs to see if anything unusual is going on around the time the system GUI and SSH services stop working?

 

[Don Intellys]

Please post your full system specifications, per the Forum rules.

• motherboard make and model

SuperMicro X9DRD-7LN4F

• CPU make and model

2x Intel Xeon E5-2620

• RAM quantity

128 GB

• hard drives, quantity, model numbers, and RAID configuration

Primary (boot) drive - (2) 120 GB Intel SpeedDemon SSD model SSDSC2BB120G401 mirrored
Storage drives - (16) Western Digital RE WD4001FYYG 4TB 7200 RPM 32MB Cache SAS 6Gb/s 3.5" Enterprise Internal Hard Drive
Cache/Log drives - (4) 120 GB Intel SpeedDemon SSD model SSDSC2BB800G401

• hard disk controllers

Broadcom 2308 SAS2

• network cards

Intel® i350 Quad Port Gigabit Ethernet

• FibreChannel cards

QLogic QLE2560 single-port 8GB

Have you examined the system logs to see if anything unusual is going on around the time the system GUI and SSH services stop working?

Can you please let me know where the system logs are? I am NOT a linux expert, however, I have worked with linux and UNIX for a couple of decades to get my job done, so I am very familiar with logs and such. Can you tell me what specific logs I will need to look at?

 

[Don Intellys]

I just tried something very different I ran service netif restart and the WebUI and SSH both came back up instantly.

 

[Spearfoot]

• motherboard make and model

SuperMicro X9DRD-7LN4F

• CPU make and model

2x Intel Xeon E5-2620

• RAM quantity

128 GB

• hard drives, quantity, model numbers, and RAID configuration

Primary (boot) drive - (2) 120 GB Intel SpeedDemon SSD model SSDSC2BB120G401 mirrored
Storage drives - (16) Western Digital RE WD4001FYYG 4TB 7200 RPM 32MB Cache SAS 6Gb/s 3.5" Enterprise Internal Hard Drive
Cache/Log drives - (4) 120 GB Intel SpeedDemon SSD model SSDSC2BB800G401

• hard disk controllers

Broadcom 2308 SAS2

• network cards

Intel® i350 Quad Port Gigabit Ethernet

• FibreChannel cards

QLogic QLE2560 single-port 8GB


Can you please let me know where the system logs are? I am NOT a linux expert, however, I have worked with linux and UNIX for a couple of decades to get my job done, so I am very familiar with logs and such. Can you tell me what specific logs I will need to look at?

Thanks for the info.

The logs are located in the /var/log directory. The main logs of interest are messages and auth.log.

 

[Spearfoot]

I just tried something very different I ran service netif restart and the WebUI and SSH both came back up instantly.

But you shouldn't have to do anything like this... the WebGUI and SSH services should simply be running all of the time. Have you made any changes to any system configuration files outside of the WebGUI?

 

[Don Intellys]

Okay, everybody. While going through the tabs on the WebUI, I discovered that there was no "default route" which I thought was very odd because the UI clearly showed under the networking tab the gateway being correct. So, I edited the configuration, changed the gateway from 10.1.6.254 to 10.1.6.253 and saved it. Then I changed it back to 10.1.6.254 and default route suddenly showed up everywhere, correctly. Message log:
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: delete net default: gateway 10.1.6.253 fib 0: not in table
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: delete net fe80::: gateway ::1
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: delete net ff02::: gateway ::1
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: delete net ::ffff:0.0.0.0: gateway ::1
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: delete net ::0.0.0.0: gateway ::1
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: add net default: gateway 10.1.6.253
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: add net fe80::: gateway ::1
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: add net ff02::: gateway ::1
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: add net ::ffff:0.0.0.0: gateway ::1
Jun 27 10:43:58 GV1-MGMT-SAN01 notifier: add net ::0.0.0.0: gateway ::1

Since I did that, I have not had any more problems.

 

[Don Intellys]

In addition, I also looked at the DNS entries. That was set to 10.1.6.10. I opened the resolv.conf file and it showed nameserver 127.0.0.1. I manually edited that and now I can resolve hostnames (such as to check for an update).

This is the fourth time I have tested loading FreeNAS on this device. Every time, I found that the WebUI timeout occurred. Now that I know the basic network interface settings were showing up in the WebUI, however, were not correct on the base OS, I will be able to reproduce this problem.