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

ReadyNas Duo V1 update to 4.1.14 failed Frontview.

viperhansa
Virtuoso

ReadyNas Duo V1 update to 4.1.14 failed Frontview.

Hi all.

I had a Duo set up and running well (as well it could since its a Duo) and logged in to Frontview.
Got a message that i had a update to install 4.1.14, installed that, all worked well, got the restart nas to complete the update, did that.

All is well so far, i can see all shares, i can access it thru ssh (winscp), i can access my installed apps (sabnzb / Sickbeard / transmisson) without problem.
BUT i can not access Frontview, ERR_CONNECTION_REFUSED is what i get.

Any ideas how to fix this? I do not want to start over since i have a lot of configuring to do in that case.... 😞

Best regards

// Hans
Message 1 of 16
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.


# df -h
# df -i
# tail -n 20 /var/log/frontview/error.log
Message 2 of 16
viperhansa
Virtuoso

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

/$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdc1 1.9G 640M 1.3G 33% /
tmpfs 16k 0 16k 0% /USB
/dev/c/c 1.8T 102G 1.7T 6% /c
/c/media 1.8T 102G 1.7T 6% /home/ftp/media
/c/tv-series 1.8T 102G 1.7T 6% /home/ftp/tv-series

/$ df -i
Filesystem Inodes IUsed IFree IUse% Mounted on
/dev/hdc1 128000 15663 112337 13% /
tmpfs 7073 1 7072 1% /USB
/dev/c/c 60981248 7925 60973323 1% /c
/c/media 60981248 7925 60973323 1% /home/ftp/media
/c/tv-series 60981248 7925 60973323 1% /home/ftp/tv-series

/$ tail -n 20 /var/log/frontview/error.log
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
[Sun Jun 07 10:51:48 2015] [warn] RSA server certificate CommonName (CN) `192.168.2.26' does NOT match server name!?
PHP Fatal error: Unable to start curl module in Unknown on line 0
[Sun Jun 07 11:01:34 2015] [warn] RSA server certificate CommonName (CN) `192.168.2.26' does NOT match server name!?
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
[Sun Jun 07 11:02:13 2015] [warn] RSA server certificate CommonName (CN) `192.168.2.26' does NOT match server name!?
PHP Fatal error: Unable to start curl module in Unknown on line 0
[Sun Jun 07 11:26:45 2015] [warn] RSA server certificate CommonName (CN) `192.168.2.26' does NOT match server name!?
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/get_handler.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/get_handler.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/get_handler.pm line 2.
[Sun Jun 07 11:27:23 2015] [warn] RSA server certificate CommonName (CN) `192.168.2.26' does NOT match server name!?
PHP Fatal error: Unable to start curl module in Unknown on line 0

Sorry for NOT posting logs.. My bad.. i'm a moron.. 🙂
Message 3 of 16
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

Have you tried installing your add-ons over the top of themselves to see if that helps?
Message 4 of 16
viperhansa
Virtuoso

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

No, since I can't access frontview it's a bit hard to do that.
Message 5 of 16
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

You can install them via SSH:

# cd /tmp
# mkdir temp123
# cd temp123
# wget url
# ls
# dd if=filename.bin | tar -xv
# sh install.sh
Message 6 of 16
viperhansa
Virtuoso

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

Ok, will try..
Message 7 of 16
viperhansa
Virtuoso

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

Hi again.

i have tried re-install 1 by 1 and test if the frontview comes up and no luck there. No Frontview access.

Hoa-nas-Duo:~# tail -n 20 /var/log/frontview/error.log
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
Bad free() ignored (PERL_CORE) at /frontview/lib/Frontview.pm line 2.
[Mon Jun 08 21:14:03 2015] [warn] pid file /var/log/frontview/apache-ssl.pid ove rwritten -- Unclean shutdown of previous Apache run?
[Mon Jun 08 21:14:03 2015] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/ 0.9.8e DAV/2 PHP/5.3.29-0rnx1 mod_apreq2-20051231/2.6.0 mod_perl/2.0.3 Perl/v5.8 .8 configured -- resuming normal operations
[Mon Jun 08 21:16:28 2015] [notice] Graceful restart requested, doing restart
apache-ssl: Could not reliably determine the server's fully qualified domain nam e, using 192.168.2.26 for ServerName
[Mon Jun 08 21:16:40 2015] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/ 0.9.8e DAV/2 PHP/5.3.29-0rnx1 mod_apreq2-20051231/2.6.0 mod_perl/2.0.3 Perl/v5.8 .8 configured -- resuming normal operations
[Mon Jun 08 21:18:17 2015] [notice] Graceful restart requested, doing restart
apache-ssl: Could not reliably determine the server's fully qualified domain nam e, using 192.168.2.26 for ServerName
[Mon Jun 08 21:18:42 2015] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/ 0.9.8e DAV/2 PHP/5.3.29-0rnx1 mod_apreq2-20051231/2.6.0 mod_perl/2.0.3 Perl/v5.8 .8 configured -- resuming normal operations
[Mon Jun 08 21:19:31 2015] [notice] Graceful restart requested, doing restart
apache-ssl: Could not reliably determine the server's fully qualified domain nam e, using 192.168.2.26 for ServerName
[Mon Jun 08 21:19:48 2015] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/ 0.9.8e DAV/2 PHP/5.3.29-0rnx1 mod_apreq2-20051231/2.6.0 mod_perl/2.0.3 Perl/v5.8 .8 configured -- resuming normal operations
[Mon Jun 08 21:22:00 2015] [notice] Graceful restart requested, doing restart
apache-ssl: Could not reliably determine the server's fully qualified domain nam e, using 192.168.2.26 for ServerName
[Mon Jun 08 21:22:14 2015] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/ 0.9.8e DAV/2 PHP/5.3.29-0rnx1 mod_apreq2-20051231/2.6.0 mod_perl/2.0.3 Perl/v5.8 .8 configured -- resuming normal operations
[Mon Jun 08 21:23:27 2015] [notice] Graceful restart requested, doing restart
apache-ssl: Could not reliably determine the server's fully qualified domain nam e, using 192.168.2.26 for ServerName
[Mon Jun 08 21:24:00 2015] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/ 0.9.8e DAV/2 PHP/5.3.29-0rnx1 mod_apreq2-20051231/2.6.0 mod_perl/2.0.3 Perl/v5.8 .8 configured -- resuming normal operations
[Mon Jun 08 21:28:15 2015] [notice] caught SIGTERM, shutting down
Hoa-nas-Duo:~#



// Hans
Message 8 of 16
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

That PHP add-on is an old version. Can you try the latest version of the add-on?: https://rnxtras.com/addons/php-5-4-readynas-4-sparc

Which add-ons do you have installed?
Message 9 of 16
viperhansa
Virtuoso

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

I have:
Php, myphpadmin, sqlon, sickbeard, sabnzb, transmission, couchpotato...
some more I can't remember.
can check when Im home again.

Sent from my phone.
Message 10 of 16
viperhansa
Virtuoso

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

mdgm wrote:
That PHP add-on is an old version. Can you try the latest version of the add-on?: https://rnxtras.com/addons/php-5-4-readynas-4-sparc

Which add-ons do you have installed?


seems to solved the problem.
strange since i was running the old prior to the update.

Thanks for the as always great support!!
Message 11 of 16
viperhansa
Virtuoso

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

viperhansa wrote:
mdgm wrote:
That PHP add-on is an old version. Can you try the latest version of the add-on?: https://rnxtras.com/addons/php-5-4-readynas-4-sparc

Which add-ons do you have installed?


seems to solved the problem.
strange since i was running the old prior to the update.

Thanks for the as always great support!!


EDIT:

Spoke to quickly, now i cannot access SickBeard.... "connection refused"
Message 12 of 16
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

That's a lot of add-ons to run on a Sparc NAS. Are you sure you need them all?

What's the memory usage like? Is the memory swapping?
Message 13 of 16
viperhansa
Virtuoso

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

I am not running them at the same time.
only running 24/7 is sickbeard and sabnzb.
And php
Message 14 of 16
mdgm-ntgr
NETGEAR Employee Retired

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

Sounds like the Sickbeard service is not starting. You may wish to check the logs from sickbeard to look for clues as to why.
Message 15 of 16
viperhansa
Virtuoso

Re: ReadyNas Duo V1 update to 4.1.14 failed Frontview.

Hi mdgm...

It looks like sickbeard IS starting, i have logs adding up with searches and such..
Jun-13 13:47:16 DEBUG MAIN :: Executing git symbolic-ref -q HEAD with your shell in /usr/share/sickbeard
Jun-13 13:47:16 DEBUG MAIN :: git output: fatal: Not a git repository (or any parent up to mount parent )
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).

Jun-13 13:47:16 DEBUG MAIN :: Unable to find git with command git symbolic-ref -q HEAD
Jun-13 13:47:16 DEBUG MAIN :: Retrieving the last check time from the DB

Jun-13 13:47:16 DEBUG MAIN :: sickbeard.db: SELECT * FROM info
Jun-13 13:47:17 INFO MAIN :: Starting Sick Beard on http://0.0.0.0:8888/
Jun-13 13:47:20 INFO MAIN :: Loading initial show list
Jun-13 13:47:20 DEBUG MAIN :: sickbeard.db: SELECT * FROM tv_shows
Jun-13 13:47:20 DEBUG SEARCH :: Starting new thread: SEARCH
Jun-13 13:47:20 DEBUG BACKLOG :: Starting new thread: BACKLOG
Jun-13 13:47:20 DEBUG BACKLOG :: Retrieving the last check time from the DB
Jun-13 13:47:20 DEBUG BACKLOG :: sickbeard.db: SELECT * FROM info
Jun-13 13:47:20 DEBUG BACKLOG :: Air-by-date segments: []
Jun-13 13:47:20 DEBUG BACKLOG :: Setting the last backlog in the DB to 735762
Jun-13 13:47:20 DEBUG BACKLOG :: sickbeard.db: SELECT * FROM info


Seems like it is some access to the webpage that have changed.. ??
Message 16 of 16
Top Contributors
Discussion stats
  • 15 replies
  • 3524 views
  • 2 kudos
  • 2 in conversation
Announcements