Orbi WiFi 7 RBE973
Reply

Readynas Apache2 issues

SAS1201
Aspirant

Readynas Apache2 issues

I am having issues recently since I upgraded to 6.10.1.  First of the images on the Admin web portal are not loading for the APPS that I have running.  The next issue, is I have a few apps that are not working - web based and it appears the apache server is not working.  See below. 
Also when i try to update everything all via apt-get, nothing working, as I keep getting errors. .

 

Anything you know about this.. Is there a fix I missed? 

 

apache2.service - The Apache HTTP Server
Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2019-06-12 14:43:42 EDT; 2h 54min ago
Process: 10534 ExecStart=/usr/sbin/apachectl start (code=exited, status=1/FAILURE)
Process: 10440 ExecStartPre=/frontview/bin/fvapps (code=exited, status=0/SUCCESS)

Jun 12 14:43:40 Toychest systemd[1]: Starting The Apache HTTP Server...
Jun 12 14:43:42 Toychest apachectl[10534]: apache2: Syntax error on line 200 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/php5.load: Cannot load /usr/lib/apache2/modul
es/libphp5.so into server: /usr/lib/apache2/modules/libphp5.so: undefined symbol: unixd_config
Jun 12 14:43:42 Toychest apachectl[10534]: Action 'start' failed.
Jun 12 14:43:42 Toychest apachectl[10534]: The Apache error log may have more information.
Jun 12 14:43:42 Toychest systemd[1]: apache2.service: Control process exited, code=exited status=1
Jun 12 14:43:42 Toychest systemd[1]: Failed to start The Apache HTTP Server.
Jun 12 14:43:42 Toychest systemd[1]: apache2.service: Unit entered failed state.
Jun 12 14:43:42 Toychest systemd[1]: apache2.service: Triggering OnFailure= dependencies.
Jun 12 14:43:42 Toychest systemd[1]: apache2.service: Failed with result 'exit-code'.

Model: RN102|ReadyNAS 100 Series 2- Bay
Message 1 of 9
StephenB
Guru

Re: Readynas Apache2 issues

I believe the issue is due to your apps - particularly php.  

 

You might want to connect with @WhoCares_ - perhap via his site https://rnxtras.com/

 

He has a php update that is compatible with 6.10.x there.

Message 2 of 9
WhoCares_
Mentor

Re: Readynas Apache2 issues

Hi Stephen,

 

Although I'm happy to see my add-ons used, the solution may be easier. What most likely happened here is that one or other add-on required PHP so it got installed from the official repo. Now I suspect that for some reason NTGR themselves forgot to build a new version of PHP5 that would work with Apache 2.4 as is shipping since 6.10.0 and include that version into the 6.10.x repos.

That said, there's also a chance that they actually built a new version but I don't think any packages already existing on the system would get upgraded on a firmware upgrade, essentially leading to the same problem. If NTGR did upgrade the PHP5 packages the solution to the problem would be as easy as

  • logging into the NAS using SSH
  • issuing "apt update && apt full-upgrade" and after that has finished
  • "systemctl restart apache2"

 

-Stefan

Message 3 of 9
SAS1201
Aspirant

Re: Readynas Apache2 issues

Thanks, when I try the apt update && apt full-upgrade as suggested and I am getting errors.. Any ideas?

 


Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
Fetched 15.7 kB in 2s (6,316 B/s)
Reading package lists... Done
E: Failed to fetch http://mirrors.kernel.org/debian/dists/jessie/InRelease Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: Failed to fetch http://security.debian.org/dists/jessie/updates/InRelease Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)
E: Some index files failed to download. They have been ignored, or old ones used instead.

Message 4 of 9
WhoCares_
Mentor

Re: Readynas Apache2 issues

Sounds like you're behind a proxy. What you can try is to tell apt to use that proxy by 

 

- creating the file /etc/apt/apt.conf.d/00_proxy (using "vi /etc/apt/apt.conf.d/00_proxy")

- add the following lines:

Acquire::http::proxy "http://<proxy>";
Acquire::https::proxy "https://<proxy>";
Acquire::ftp::proxy "ftp://<proxy>";
Acquire::socks::proxy "socks:<proxy>";

(replace <proxy> with the actual location of the proxy you're using.

- save the file

- try the "apt update && apt full-upgrade" again

 

-Stefan

Message 5 of 9
WhoCares_
Mentor

Re: Readynas Apache2 issues

Smiley replacements in code blocks. Really, now?

 

-Stefan

Message 6 of 9
StephenB
Guru

Re: Readynas Apache2 issues


@WhoCares_ wrote:

Smiley replacements in code blocks. Really, now?


I've complained about it, and I think fixing it is on Lithium's "to do" list.

 

There is a fairly unobtrusive work-around which I applied to your post.  That's to bold the :s that signal the emoticons

Message 7 of 9
SAS1201
Aspirant

Re: Readynas Apache2 issues

Thanks for the help, I tried this and getting all different types of errors now. 

Assuming the proxy is my firewall/GW - Private LAN IP address -

 

I am now getting this error..

E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily unavailable)
E: Unable to lock directory /var/lib/apt/lists/

 

Message 8 of 9
WhoCares_
Mentor

Re: Readynas Apache2 issues

"All different types of errors" is a bit vague but the one you posted can be safely ignored. It normally means that the ReadyNAS itself was running the apt tool to check for "automatic updates". To make sure that no two processes write to the package database at the same time the apt tool will "lock" the file and that's (basically, it really is a bit more complicated than that) what the error message is telling you. If that happens just run your command again a minute later or so it should work then.

 

As for the firewall: that depends on whether the firewall actually has a proxy capability (most do) and of course on whether it is turned on. If it is that would mean you'd have to give your PC a proxy configuration for accessing the internet as well. That's what you'd have to enter for the <proxy> placeholder in my snippet above.

 

-Stefan

Message 9 of 9
Top Contributors
Discussion stats
  • 8 replies
  • 2605 views
  • 0 kudos
  • 3 in conversation
Announcements