× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: ReadyNAS 516 on OS 6.7.1 - Unable to access admin page

Osnofla
Aspirant

ReadyNAS 516 on OS 6.7.1 - Unable to access admin page

Dear Netgear Community and Support!

 

After manually installing php 5.3 via ssh and apt-get I somehow managed to break the admin webpage.

 

Otherwise the NAS is still running fine under OS 6.7.1, I have ssh access, apps are running and file shares are available. RAIDar and ReadyCloud both find the NAS online.

 

But when accessing https://<ip>/admin a 404 Not Found error page from apache2 on port 80

 

The reason could be that I also installed/upgraded apache2, which might have messed up the apache2.conf (or other conf files) to point to the admin/ directory in the http-root. However, with find / -type d -name 'admin' I cant find anything that looks like the sources for the admin page.

 

Any thoughts on what I need to check or to do to restore the Netgear admin page?

Model: RN51600|ReadyNAS 516 6-Bay
Message 1 of 6
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNAS 516 on OS 6.7.1 - Unable to access admin page

You'd need to look under e.g. /etc/apache2

 

Comparing with what you see running the OS6 Virtual Machine in VirtualBox should help point you in the right direction.

 

Welcome to the community!

Message 2 of 6
Osnofla
Aspirant

Re: ReadyNAS 516 on OS 6.7.1 - Unable to access admin page

Hi mdgm!

 

Thanks for the hint to work with VirtualBox and to compare vanilla OS 6.0.6 with my current build.

The files at /etc/frontview and the respective .conf files are still there, that's the good news!

 

Comparing the apache2 setup I noticed two differences:

 

1) Links within /sites-enabled: like in vanilla OS 6 I have two links:

 

000-fv-http -> /etc/apache2/sites-available/fv-http
000-fv-https -> ../sites-available/fv-https

but 000-fv-http differs from vanilla OS6, which points to ../sites-available/fv-http-admin

000-fv-http -> ../sites-available/fv-http-admin
000-fv-https -> ../sites-available/fv-https

changing this and restarting apache2 unfortunately did not change anything, still getting a 404 when requesting http://<ip>/admin

 

 

2) Comparing the /etc/apache2/apache2.conf I noticed another difference:

Below section is completly missing in vanilla OS 6:

 

# Sets the default security model of the Apache2 HTTPD server. It does
# not allow access to the root filesystem outside of /usr/share and /var/www.
# The former is used by web applications packaged in Debian,
# the latter may be used for local directories served by the web server. If
# your system is serving content from a sub-directory in /srv you must allow
# access here, or in any related virtual host.
<Directory />
      Options FollowSymLinks
      AllowOverride None
      Require all denied
</Directory>

<Directory /usr/share>
     AllowOverride None
     Require all granted
</Directory>

<Directory /var/www/>
      Options Indexes FollowSymLinks
      AllowOverride None
      Require all granted
</Directory>

#<Directory /srv/>

#<Directory /srv/>
#       Options Indexes FollowSymLinks
#       AllowOverride None
#       Require all granted
#</Directory>




# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives.  See also the AllowOverride
# directive.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<FilesMatch "^\.ht">
        Require all denied
</FilesMatch>

 

Further, below section is different in vanila than my current config:

 

# Include of directories ignores editors' and dpkg's backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf
#vanilla OS 6# Include conf.d/

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf
#vanilla OS 6# Include sites-enabled/

 

Changing my apache2.conf file to the one from vanilla OS 6 (disabling via # comment the section above and changing the IncludeOptional directives to the Include directives) leads to apache2 not being able to start anymore with the following error message:

 

 

Job for apache2.service failed because the control process exited with error code.
See "systemctl status apache2.service" and "journalctl -xe" for details.
root@NASty:/etc/apache2# systemctl status apache2.service
● apache2.service - The Apache HTTP Server
   Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
  Drop-In: /lib/systemd/system/apache2.service.d
           └─forking.conf
   Active: failed (Result: exit-code) since Sat 2017-05-27 12:27:14 CEST; 7s ago
  Process: 27739 ExecStart=/usr/sbin/apache2 $OPTIONS -k start (code=exited, status=1/FAILURE)
  Process: 27628 ExecStartPre=/frontview/bin/fvapps (code=exited, status=0/SUCCESS)
 Main PID: 19485 (code=exited, status=0/SUCCESS)

May 27 12:27:14 NASty systemd[1]: Starting The Apache HTTP Server...
May 27 12:27:14 NASty apache2[27739]: apache2: Syntax error on line 217 of /etc/apache2/apache2.conf: Syntax error on
 line 10 of /etc/apache2/conf.d/FSSHARE_data: Syntax error on line 2 of /etc/frontview/apache/Auth.conf: Cannot load
/usr/lib/apache2/modules/mod_privsep.so into server: /usr/lib/apache2/modules/mod_privsep.so: cannot open shared obje
ct file: No such file or directory
May 27 12:27:14 NASty systemd[1]: apache2.service: Control process exited, code=exited status=1
May 27 12:27:14 NASty systemd[1]: Failed to start The Apache HTTP Server.
May 27 12:27:14 NASty systemd[1]: apache2.service: Unit entered failed state.
May 27 12:27:14 NASty systemd[1]: apache2.service: Triggering OnFailure= dependencies.
May 27 12:27:14 NASty systemd[1]: apache2.service: Failed with result 'exit-code'.

 

The file /usr/lib/apache2/modules/mod_privsep.so is indeed missing.

Could this be the reason why my setup is no longer working? Any ideas on how to install or build this module?

 

Thank you very much for your support!

 

Message 3 of 6
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNAS 516 on OS 6.7.1 - Unable to access admin page

If you can get things mostly the same an OS extraction hopefully will do the rest.

# touch /.os_update
# rn_shutdown -r

Note I'd update the VM to the same firmware version you're running on the NAS before doing the comparison. 6.0.6 is extremely old firmware.

 

You may want to do a

# dpkg -l

and compare what apache packages are installed as well.

 

In future it would be a good idea to experiment on the VM before making changes on your production system.

Message 4 of 6
Osnofla
Aspirant

Re: ReadyNAS 516 on OS 6.7.1 - Unable to access admin page

I've setup the VM with the firmware 6.6.0 (not 6.0.6, sorry that was a typo), however updating the VM to 6.7.1 makes sense before comparing the package lists.

Unfortunately the update with touch /.os_update and rn_shutdown -r did not work on the VM, although it has access to the web (ping to any website and apt-get update works)

 

Are there any specific steps required to update in VM? Or is there a procedure vis ssh/console to download the image file (eg from https://kb.netgear.com/000038557/ReadyNAS-OS-6-Software-Version-6-7-1 ) and then to trigger the upgrade from the console?

 

Running touch /.os_update and rn_shutdown -r on the real NAS did also not work, no updates were made. Maybe due to conflicts with some packages? Need to do the package/version comparison to find out...

 

Thank you very much for your support so far!

 

Message 5 of 6
Osnofla
Aspirant

Re: ReadyNAS 516 on OS 6.7.1 - Unable to access admin page

I found the following commands on this forum to manually download & trigger a firmware update, which worked also on VirtualBox:

 

cd /var/readynasd
wget http://www.downloads.netgear.com/files/GDC/READYNAS-300/ReadyNASOS-6.7.1-x86_64.zip
unzip *.zip
echo /var/readynasd/ReadyNASOS-6.7.1-x86_64.img > /etc/.flash_update
rn_shutdown -r

 

 

However, afterwards comparing the package lists on both VirtualBox and my NAS did not show any differences. I then tried apt-get -f install but this also didnt help. I then upgraded successfully my NAS to the most recent OS version 6.7.4, but this did also not help. Trying to start apache2 service always crashed due to missing dependencies, being mod_auth_token.so not found.

 

I then decided to try a clean install of apache2 by running:

 

apt-get remove --purge apache2*

apt-get --reinstall install apache2.2-common
apt-get --reinstall install apache2

 

 

Unfortunately the configuration of apache2.2-common fails with the error message "ERROR: Site default does not exist!"

 

root@NASty:/etc/apache2# apt-get --reinstall install apache2.2-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  apache2-utils apache2.2-bin
Suggested packages:
  www-browser apache2-doc apache2-suexec | apache2-suexec-custom
Recommended packages:
  ssl-cert
The following NEW packages will be installed:
  apache2-utils apache2.2-bin apache2.2-common
0 upgraded, 3 newly installed, 0 to remove and 105 not upgraded.
Need to get 0 B/1,258 kB of archives.
After this operation, 6,747 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package apache2-utils.
(Reading database ... 32152 files and directories currently installed.)
Preparing to unpack .../apache2-utils_2.2.32-0.netgear1_amd64.deb ...
Unpacking apache2-utils (2.2.32-0.netgear1) ...
Selecting previously unselected package apache2.2-bin.
Preparing to unpack .../apache2.2-bin_2.2.32-0.netgear1_amd64.deb ...
Unpacking apache2.2-bin (2.2.32-0.netgear1) ...
Selecting previously unselected package apache2.2-common.
Preparing to unpack .../apache2.2-common_2.2.32-0.netgear1_amd64.deb ...
Unpacking apache2.2-common (2.2.32-0.netgear1) ...
Processing triggers for systemd (230-7~bpo8+2.netgear2) ...
Setting up apache2-utils (2.2.32-0.netgear1) ...
Setting up apache2.2-bin (2.2.32-0.netgear1) ...
Setting up apache2.2-common (2.2.32-0.netgear1) ...
ERROR: Site default does not exist!
dpkg: error processing package apache2.2-common (--configure):
 subprocess installed post-installation script returned error exit status 1
Processing triggers for systemd (230-7~bpo8+2.netgear2) ...
Errors were encountered while processing:
 apache2.2-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

 

Message 6 of 6
Top Contributors
Discussion stats
  • 5 replies
  • 4140 views
  • 1 kudo
  • 2 in conversation
Announcements