NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
ReadyNAS 628x Interface hangs while change NFS/SMB permissions
When making a change to NFS or SMB permissions, the interface will hang upon commiting a change. The busy wheel spins indefinitely until I close and reopen the browser - see attached. Navigation in...
Did you disable ipv6 in the network settings as I suggested above?
Are you using iSCSI LUNs?
FWIW, I am thinking that it might be a good idea to try an OS reinstall.
It might be interesting to see if apache2 can be restarted manually (before the error). For instance, do a journalctl -f in one ssh window, and then do a systemctl restart apache2 in a second window, and see what happens.
Sandshark wrote:
When you log into the admin UI, are you using the NAS name or IP address? I don't know exactly why that might work, but it could be associated with the FQDN issue.
The AH00558 is coming from the apache2 restart, so it's not related to how you access the NAS in the browser.
The normal workaround is to add a ServerName directive to apache2.conf (which can either specify an IP address or an FQDN). In fact, the error message says to do that. In this particular case, the AH00558 error is specific to the IPv6 address fe80::b2b9:8aff:fe44:d36c. This is a link local address (self assigned by the NAS). If ipv6 isn't enabled in the router, it's a good idea to disable ipv6. Though you'll likely still see that error, it will just shift to an ipv4 address (see below).
But the real questions here are
- why apache2 is trying to restart in the first place
- why the restart is failing (or looping)
The web ui is clearly hanging because apache2 isn't up.
FWIW, I tried manually starting apache2 on my own NAS, and this is what I see in journalctl -f
Oct 29 06:07:25 NAS systemd[1]: Stopping The Apache HTTP Server... Oct 29 06:07:25 NAS systemd[1]: Reloading. Oct 29 06:07:26 NAS systemd[1]: nut-monitor.service: Supervising process 6027 which is not our child. We'll most likely not notice when it exits. Oct 29 06:07:26 NAS apachectl[30926]: [Thu Oct 29 06:07:26.096421 2020] [so:warn] [pid 30929] AH01574: module cgi_module is already loaded, skipping Oct 29 06:07:26 NAS apachectl[30926]: AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/001-fv-https2.conf:2 Oct 29 06:07:26 NAS apachectl[30926]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.0.15. Set the 'ServerName' directive globally to suppress this message Oct 29 06:07:26 NAS systemd[1]: Stopped The Apache HTTP Server. Oct 29 06:07:26 NAS systemd[1]: Starting The Apache HTTP Server... Oct 29 06:07:26 NAS systemd[1]: Reloading. Oct 29 06:07:26 NAS systemd[1]: nut-monitor.service: Supervising process 6027 which is not our child. We'll most likely not notice when it exits. Oct 29 06:07:26 NAS apachectl[31035]: [Thu Oct 29 06:07:26.432460 2020] [so:warn] [pid 31039] AH01574: module cgi_module is already loaded, skipping Oct 29 06:07:26 NAS apachectl[31035]: AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/001-fv-https2.conf:2 Oct 29 06:07:26 NAS apachectl[31035]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.0.15. Set the 'ServerName' directive globally to suppress this message Oct 29 06:07:26 NAS apache2[31039]: [ssl:warn] [pid 31039] AH01909: 10.0.0.15:50020:0 server certificate does NOT include an ID which matches the server name Oct 29 06:07:26 NAS apache2[31039]: [ssl:warn] [pid 31039] AH01909: 10.0.0.15:443:0 server certificate does NOT include an ID which matches the server name Oct 29 06:07:26 NAS systemd[1]: Started The Apache HTTP Server. Oct 29 06:07:26 NAS apache2[31043]: [ssl:warn] [pid 31043] AH01909: 10.0.0.15:50020:0 server certificate does NOT include an ID which matches the server name Oct 29 06:07:26 NAS apache2[31043]: [ssl:warn] [pid 31043] AH01909: 10.0.0.15:443:0 server certificate does NOT include an ID which matches the server name
This looks very similar to what bradthur is seeing. There were two restarts though, which is curious. But not an endless loop (as he has).
Plex is off in my case, so I'm wouldn't expect to see the plex error (though I have seen it before, and I haven't seen an endless restart).
I'm also not seeing this:
Oct 27 18:13:52 NAS01 systemd-sysv-generator[13852]: Overwriting existing symlink /run/systemd/generator.late/umountiscsi.service with real service.
Though I'm not running iSCSI. All I see in the generator.late folder is this:
root@NAS:~# ls -al /run/systemd/generator.late/* -rw-r--r-- 1 root root 444 Oct 29 06:07 /run/systemd/generator.late/hdparm.service root@NAS:~#
Have you downloaded the log zip file, and looked there?
What firmware are you running?
What apps do you have installed?
Is the system resyncing?
Firmware: 6.10.3
Apps: Plex - Remote access disabled
Resync: No
Log Zip:
I spent some time analyzing the logs and have combined the fail/errors/logname in the attached file. Admitfully, the logs aren't very helpful to me although, they did point me in the direction of discovering a time delta of about 4 minutes. I have since synced up everything with a common ntp server(s). I used to have active directory enabled but ended up diabling because of the inability to manage the device - Not sure how the time would impact changes to NFS shares or the interface in general.
Since syncing the time and days after diabling AD integration, I still continue to have problem with the interface to the point where it's not manageable.
I also attached a screen capture of the "ReadyNAS admin Page is offline" message.
My installation is very simple, not sure how this could be so problematic.
What status are you seeing with RAIDar? https://kb.netgear.com/20684/ReadyNAS-Downloads
Note there is also the ability to run a diag from RAIDar.
Says no errors found. I'm at a loss here.
Do you have ssh enabled? If not, you could try rebooting the NAS, and if that restores admin access you could enable ssh.
The web server runs at a lower priority than other services, and if something is taking up too much resources that could interfere with access. ssh would give you more abilility to see what is going on (assuming you have some familiarity with linux commands).
Plex could be part of the puzzle, as it can take a lot of resources when it is gathering metadata for your libraries. But it seems unlikely that would stall a 628x. Also, I am wondering how many NFS threads you have configured for the NAS. If you've increased the default value of 4, you might try lowering that back to the default.
Have you looked at the amount of free space in the OS partition? Look at volume.log in the log zip file. Scroll down to the df -h section.
=== df -h === Filesystem Size Used Avail Use% Mounted on udev 10M 4.0K 10M 1% /dev /dev/md0 4.0G 1012M 2.8G 27% / ...
/dev/md0 is the OS partition, and if it does get full it can cause a variety of misbehaviors. Normally it will have about 75% free space, even with plex installed.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
