Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Re: Frontview not accessible after RAIDiator 4.1.13 upgrade
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2013-12-31
10:14 AM
2013-12-31
10:14 AM
Frontview not accessible after RAIDiator 4.1.13 upgrade
Hi everyone
I hope that you can help with this strange problem. I upgraded my ReadyNAS NV+ to the latest firmware yesterday and since then have been unable to access Frontview via any browser: the browser replies that it is unable to access the network although I have full access to all files via explorer.
My ReadyNAS is on static local IP 192.168.0.25.
I tried to reinstall the firmware but that made no difference.
Before coming here I tried to search for a solution. I can SSH to the ReadyNAS and when following an old thread with a similar problem I tried to restart the apache service but that resulted in the following:
ReadyNAS1:~# /etc/init.d/frontview restart
Stopping frontview: apache-sslNo /usr/sbin/apache-ssl found running; none killed.
Starting frontview: apache-sslapache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.0.25 for ServerName
(48)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
I really have almost no knowledge of this topic and was hoping that someone on this forum could accurately interpret what this all means and how to resolve it?
Thanks very much
I hope that you can help with this strange problem. I upgraded my ReadyNAS NV+ to the latest firmware yesterday and since then have been unable to access Frontview via any browser: the browser replies that it is unable to access the network although I have full access to all files via explorer.
My ReadyNAS is on static local IP 192.168.0.25.
I tried to reinstall the firmware but that made no difference.
Before coming here I tried to search for a solution. I can SSH to the ReadyNAS and when following an old thread with a similar problem I tried to restart the apache service but that resulted in the following:
ReadyNAS1:~# /etc/init.d/frontview restart
Stopping frontview: apache-sslNo /usr/sbin/apache-ssl found running; none killed.
Starting frontview: apache-sslapache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.0.25 for ServerName
(48)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down
Unable to open logs
I really have almost no knowledge of this topic and was hoping that someone on this forum could accurately interpret what this all means and how to resolve it?
Thanks very much
Message 1 of 7
Labels:
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-02
01:05 AM
2014-01-02
01:05 AM
Re: Frontview not accessible after RAIDiator 4.1.13 upgrade
Which Readynas do you have? I have had the web admin screen break when I tried upgrading very old systems like the X6/600.
Message 2 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-02
01:10 AM
2014-01-02
01:10 AM
Re: Frontview not accessible after RAIDiator 4.1.13 upgrade
Any add-ons installed?
# tail -n 20 /var/log/frontview/error.log
Message 3 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-02
08:35 AM
2014-01-02
08:35 AM
Re: Frontview not accessible after RAIDiator 4.1.13 upgrade
Hi and thanks for your replies
@armornone: I have the original ReadyNAS NV+ v1
@mdgm: As far as I can recall, I believe that I installed the two php add-ons (PHPmyadmin and PHP addon although I was never able to get this to work as I wished) and the enable root SSH. I do apologise but I have almost no knowledge of the code one uses here but I'll type that line in this evening and let you know the results later.
Best Regards
@armornone: I have the original ReadyNAS NV+ v1
@mdgm: As far as I can recall, I believe that I installed the two php add-ons (PHPmyadmin and PHP addon although I was never able to get this to work as I wished) and the enable root SSH. I do apologise but I have almost no knowledge of the code one uses here but I'll type that line in this evening and let you know the results later.
Best Regards
Message 4 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-02
12:12 PM
2014-01-02
12:12 PM
Re: Frontview not accessible after RAIDiator 4.1.13 upgrade
Hi mdgm
This is what happened when I tried that code:
ReadyNAS1:~# tail -n 20 /var/log/frontview/error.log
Bad free() ignored (PERL_CORE) at (eval 2) line 3.
PHP Fatal error: Unable to start curl module in Unknown on line 0
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.
PHP Fatal error: Unable to start curl module in Unknown on line 0
Bad free() ignored (PERL_CORE) at (eval 2) line 3.
PHP Fatal error: Unable to start curl module in Unknown on line 0
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.
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.
Bad free() ignored (PERL_CORE) at (eval 3) line 3.
PHP Fatal error: Unable to start curl module in Unknown on line 0
Are you able to interpret this and let me know what the solution is please?
Thanks very much
This is what happened when I tried that code:
ReadyNAS1:~# tail -n 20 /var/log/frontview/error.log
Bad free() ignored (PERL_CORE) at (eval 2) line 3.
PHP Fatal error: Unable to start curl module in Unknown on line 0
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.
PHP Fatal error: Unable to start curl module in Unknown on line 0
Bad free() ignored (PERL_CORE) at (eval 2) line 3.
PHP Fatal error: Unable to start curl module in Unknown on line 0
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.
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.
Bad free() ignored (PERL_CORE) at (eval 3) line 3.
PHP Fatal error: Unable to start curl module in Unknown on line 0
Are you able to interpret this and let me know what the solution is please?
Thanks very much
Message 5 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-02
02:24 PM
2014-01-02
02:24 PM
Re: Frontview not accessible after RAIDiator 4.1.13 upgrade
Install the latest PHP add-on manually via SSH.
Message 6 of 7
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2014-01-03
11:14 AM
2014-01-03
11:14 AM
Re: Frontview not accessible after RAIDiator 4.1.13 upgrade
Hi mdgm,
For the benefit of anyone else reading this:
Although I really have very little idea exactly how to manually install the add-on I managed to find this article https://www.readynas.com/forum/viewtopic.php?f=65&t=71880&start=45 where you kindly advised someone else with a very similar problem. I followed the following instructions:
# cd /tmp/addons
# mkdir newphp123
# cd newphp123
# dd if=/tmp/phpaddon.bin skip=1 | tar -xv
# sh install.sh
(replacing phpaddon.bin with PHP5_5.3.27-sparc-4.4.3.bin)
...and I now have Frontview working again.
Thanks so much and happy new year
For the benefit of anyone else reading this:
Although I really have very little idea exactly how to manually install the add-on I managed to find this article https://www.readynas.com/forum/viewtopic.php?f=65&t=71880&start=45 where you kindly advised someone else with a very similar problem. I followed the following instructions:
# cd /tmp/addons
# mkdir newphp123
# cd newphp123
# dd if=/tmp/phpaddon.bin skip=1 | tar -xv
# sh install.sh
(replacing phpaddon.bin with PHP5_5.3.27-sparc-4.4.3.bin)
...and I now have Frontview working again.
Thanks so much and happy new year
Message 7 of 7