Support and News Forum

digital wrote: ↑

Sun Aug 27, 2017 1:20 pm

Hi all,

I had an issue initially when upgrading to version 2.0.3-76 whereby Apache Server not starting automatically when Ubuntu Server boots up. I had to start it manually each time. Then I thought upgrading to version 2.0.3-77 will fix the issue but it was not. I tried uninstalling apache2 "sudo apt-get purge apache2" and reinstall EvE-NG with "DEBIAN_FRONTEND=noninteractive apt-get -y install eve-ng" where it also installed the Apache Server again but when i try to open up the GUI i get this error:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@unl01.example.com to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

The apache log file says:

/var/log/apache2/error.log
[Sun Aug 27 21:04:41.263743 2017] [mpm_event:notice] [pid 7752:tid 139976340199296] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Sun Aug 27 21:04:41.263828 2017] [core:notice] [pid 7752:tid 139976340199296] AH00094: Command line: '/usr/sbin/apache2'
[Sun Aug 27 21:04:41.661859 2017] [mpm_event:notice] [pid 7752:tid 139976340199296] AH00493: SIGUSR1 received. Doing graceful restart
[Sun Aug 27 21:04:41.665490 2017] [mpm_event:notice] [pid 7752:tid 139976340199296] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Sun Aug 27 21:04:41.665499 2017] [core:notice] [pid 7752:tid 139976340199296] AH00094: Command line: '/usr/sbin/apache2'
[Sun Aug 27 21:04:42.018488 2017] [mpm_event:notice] [pid 7752:tid 139976340199296] AH00491: caught SIGTERM, shutting down
[Sun Aug 27 21:04:43.080327 2017] [mpm_event:notice] [pid 8107:tid 140515692119936] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Sun Aug 27 21:04:43.080400 2017] [core:notice] [pid 8107:tid 140515692119936] AH00094: Command line: '/usr/sbin/apache2'
[Sun Aug 27 21:06:15.309359 2017] [mpm_event:notice] [pid 8107:tid 140515692119936] AH00493: SIGUSR1 received. Doing graceful restart
[Sun Aug 27 21:06:15.320122 2017] [mpm_event:notice] [pid 8107:tid 140515692119936] AH00489: Apache/2.4.18 (Ubuntu) configured -- resuming normal operations
[Sun Aug 27 21:06:15.320140 2017] [core:notice] [pid 8107:tid 140515692119936] AH00094: Command line: '/usr/sbin/apache2'

What should i do to fix the EvE-NG GUI? I use a bare metal server and i don't want to reinstall everything back from scratch!

Thank you in advance.

Looks like you messed up the installed packages.
When Apache not running, you can make it work by setting up start automatically every time you reboot. not to uninstall the packages.

can you do

apt-get update
apt-get dist-upgrade

See if the issue fixes.

R!

systemctl status apache2
systemctl restart apache2
journalctl -xe

Give here the output please...

E.

ecze wrote: ↑

Mon Aug 28, 2017 12:08 am

systemctl status apache2
systemctl restart apache2
journalctl -xe

Give here the output please...

E.

Hi ecze & ramindia,

Thanks a lot for your replies. Yes, after i "purged" the apache i did a re-install and tried to "update" & "dist-upgrade" but still the issue was presistant as i described earlier. Anyways, for the sake of helping anyone who may run into this issue, after I did some troubleshooting of the issue, i was able to get the EvE GUI back when i noticed some php linked files were missing in the Apache installation.

2 link files were missing in the "/etc/apache2/mods-enabled" folder: "php7.0.conf" & "php7.0.load" after recovering them and restarting the apache service, I got back the EvE GUI working.


Regardless of fixing the EvE GUI, the apache is still running on manual start, which means i have to run the "/etc/init.d/apache2 start" command each time i boot up my server.

Here are the show commands:

---------------------------------------------------------------------------------------------------------------------------------------------------------
root@MyEVE:~# systemctl enable apache2
apache2.service is not a native service, redirecting to systemd-sysv-install
Executing /lib/systemd/systemd-sysv-install enable apache2
root@MyEVE:~#
root@MyEVE:~#
root@MyEVE:~#
root@MyEVE:~# systemctl status apache2
● apache2.service - LSB: Apache2 web server
Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled)
Drop-In: /lib/systemd/system/apache2.service.d
└─apache2-systemd.conf
Active: inactive (dead) since Mon 2017-08-28 08:42:37 SGT; 9min ago
Docs: man:systemd-sysv-generator(8)

Aug 28 08:42:36 MyEVE systemd[1]: Starting LSB: Apache2 web server...
Aug 28 08:42:36 MyEVE apache2[5120]: * Starting Apache httpd web server apache2
Aug 28 08:42:36 MyEVE apache2[5120]: *
Aug 28 08:42:36 MyEVE apache2[5183]: * Stopping Apache httpd web server apache2
Aug 28 08:42:37 MyEVE apache2[5183]: *
Aug 28 08:42:37 MyEVE systemd[1]: Started LSB: Apache2 web server.
root@MyEVE:~#
root@MyEVE:~#
root@MyEVE:~# journalctl -xe
-- Subject: Unit systemd-tmpfiles-clean.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-tmpfiles-clean.service has begun starting up.
Aug 28 08:57:30 MyEVE systemd-tmpfiles[11895]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ign
Aug 28 08:57:30 MyEVE systemd[1]: Started Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/li ... temd-devel
--
-- Unit systemd-tmpfiles-clean.service has finished starting up.
--
-- The start-up result is done.
Aug 28 08:59:37 MyEVE ntpd[5254]: 188.166.176.19 local addr 192.168.0.200 -> <null>
Aug 28 08:59:39 MyEVE ntpd[5254]: 139.59.240.152 local addr 192.168.0.200 -> <null>
Aug 28 08:59:41 MyEVE ntpd[5254]: 128.199.243.248 local addr 192.168.0.200 -> <null>
Aug 28 09:01:50 MyEVE ntpd[5254]: 185.24.221.138 local addr 192.168.0.200 -> <null>
Aug 28 09:01:51 MyEVE ntpd[5254]: 103.47.76.177 local addr 192.168.0.200 -> <null>
Aug 28 09:01:53 MyEVE ntpd[5254]: 85.220.190.246 local addr 192.168.0.200 -> <null>
Aug 28 09:02:28 MyEVE /usr/lib/snapd/snapd[2140]: snapmgr.go:504: DEBUG: Next refresh scheduled for 2017-08-28 14:26:48.
Aug 28 09:02:58 MyEVE ntpd[5254]: 128.199.123.83 local addr 192.168.0.200 -> <null>
Aug 28 09:03:01 MyEVE ntpd[5254]: 94.154.96.7 local addr 192.168.0.200 -> <null>
root@MyEVE:~#
root@MyEVE:~#
root@MyEVE:~# /etc/init.d/apache2 start
[ ok ] Starting apache2 (via systemctl): apache2.service. <<<<<----------------------------After This point the EvE GUI is functional.
root@MyEVE:~#
---------------------------------------------------------------------------------------------------------------------------------------------------------

When I upgraded to the version before-last (that is version .76), i used "sudo update-rc.d apache2 enable" command to get the Apache running automatically when the server boots. However, When I upgraded to version .77 this command now has no affect and I'm back to manual start of the Apache service!

--------------------------------------------Some show log Updates---------------------------------------------------
root@MyEVE:~#
root@MyEVE:~# journalctl | tail
Aug 28 09:34:13 MyEVE systemd[1]: Configuration file /etc/systemd/system/mysql.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Aug 28 09:34:13 MyEVE systemd[1]: [/etc/systemd/system/cpulimit.service:7] Executable path is not absolute, ignoring: (/usr/bin/killall -9 cpulimit-daemon.php & /usr/bin/killall -TERM cpulimit )
Aug 28 09:34:13 MyEVE systemd[1]: Started ACPI event daemon.
Aug 28 09:34:13 MyEVE systemd[1]: Started CUPS Scheduler.
Aug 28 09:34:13 MyEVE systemd[1]: Reloading.
Aug 28 09:34:13 MyEVE systemd-sysv-generator[7075]: Configuration file /etc/systemd/system/mysql.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Aug 28 09:34:13 MyEVE systemd[1]: Configuration file /etc/systemd/system/mysql.service is marked executable. Please remove executable permission bits. Proceeding anyway.
Aug 28 09:34:13 MyEVE systemd[1]: [/etc/systemd/system/cpulimit.service:7] Executable path is not absolute, ignoring: (/usr/bin/killall -9 cpulimit-daemon.php & /usr/bin/killall -TERM cpulimit )
Aug 28 09:34:13 MyEVE systemd[1]: Started ACPI event daemon.
Aug 28 09:34:13 MyEVE systemd[1]: Started CUPS Scheduler.
root@MyEVE:~#
root@MyEVE:~#
root@MyEVE:~# apache2ctl configtest
Syntax OK
root@MyEVE:~#
root@MyEVE:~#
-------------------------------------------------------------------------------------------------------
It looks like some MySQL and the new CPUlimit feature is causing me some problems.

Any thoughts are very much appreciated.
Thank you all once again!

root@MyEVE:~# apache2ctl configtest
Syntax OK

make sense, with the output your config fixed.

R!