NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Strange issue with migration from 102 to 312
I updated from a ReadyNAS RN102 to a RN 312. I moved the volumes as detailed in the instructions. Everything worked great and the new unit came up just fine.running 6.10.3. (Nice improvement in ...
Sandshark wrote:
It sounds to me that PHP5 was remoevd, but this file was not: /etc/apache2/mods-enabled/php5.load. I'm not really versed in how apache uses such configuration files, but I think it automatically runs anything in that directory, there is no poiner to the file elsewhere that you also need to remove. Try just moving that file to a holding area and see what happens.
Since it works in the RN102, /usr/lib/apache2/modules/libphp5.so wasn't removed either (and is the arm version of the library). So PHP5 wasn't fully removed.
Still you could simply move php5.load. Make sure there's no php5.conf in the folder either. Also, you should look at the libraries php5.load is loading, and move them to the holding area also.
Lines 200, 201 in the apache2.conf are
200 IncludeOptional mods-enabled/*.load 201 IncludeOptional mods-enabled/*.conf
So you don't actually need to edit the conf file.
Still,I'd do the factory reset (painful though it is) if it were my own system.
It sounds to me that PHP5 was remoevd, but this file was not: /etc/apache2/mods-enabled/php5.load. I'm not really versed in how apache uses such configuration files, but I think it automatically runs anything in that directory, there is no poiner to the file elsewhere that you also need to remove. Try just moving that file to a holding area and see what happens.
Sandshark wrote:
It sounds to me that PHP5 was remoevd, but this file was not: /etc/apache2/mods-enabled/php5.load. I'm not really versed in how apache uses such configuration files, but I think it automatically runs anything in that directory, there is no poiner to the file elsewhere that you also need to remove. Try just moving that file to a holding area and see what happens.
Since it works in the RN102, /usr/lib/apache2/modules/libphp5.so wasn't removed either (and is the arm version of the library). So PHP5 wasn't fully removed.
Still you could simply move php5.load. Make sure there's no php5.conf in the folder either. Also, you should look at the libraries php5.load is loading, and move them to the holding area also.
Lines 200, 201 in the apache2.conf are
200 IncludeOptional mods-enabled/*.load 201 IncludeOptional mods-enabled/*.conf
So you don't actually need to edit the conf file.
Still,I'd do the factory reset (painful though it is) if it were my own system.
Moving php5.* out of the directory did the trick. THANK YOU. Much appreciated.
Scott
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
