Apache does not start automatically

maverick

Hi guys,

aaPanel running on Oracle Linux 8, this is a test server. Apache doesn't start automatically after reboot, always have to go on Control Panel and start it.
Any hints about this issue? thanks.

ganteng

maverick login to your server as root and execute : systemctl enable httpd

aaPanel_Captain

does the apache error log record startup failure information?

vhtrian

try to delete others : ngix & litespeed sv

maverick

Hi guys sorry for the delay in replies:

@aaPanel_Captain I saw no failure in the logs. Simply is not starting on boot.

@ganteng if I enable httpd in the way you suggested it will enable the distro's default httpd instead of aaPanel's httpd installed at /www/server/apache.

@vhtrian I don't have nginx nor litespeed

aaPanel_Captain

maverick execute the following command to see if there is an error in the return value, and at the same time uninstall the apache that comes with the system and try to start the apache installed by the panel.

/etc/init.d/httpd start
yum -y remove httpd

maverick

ping? .....

maverick

@aaPanel_Captain
Hi there and thank you for your reply. Sorry I didn't get back at this sooner.

So,httpd package FROM BASE is not installed. It wasn't installed from the start as we start with minimum installs and only setup the packages required by the software we'll be putting in, in this case aaPanel takes care of what it needs.

About /etc/init.d/httpd start running it starts without errors.

[root@srv ~]# /etc/init.d/httpd start
start apache...  done

which reminded me of checking if it was up to start on boot.

# chkconfig --list httpd

Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.

      If you want to list systemd services use 'systemctl list-unit-files'.
      To see services enabled on particular target use
      'systemctl list-dependencies [target]'.

httpd          	0:off	1:off	2:off	3:off	4:off	5:off	6:off

I have to say its 2021 and we've already evolved from sysV to systemd. So this felt archaic and having been directed here instead of to systemd services made me think you guys need to change the mindcept on this.
The correct place to put systemd service files is /usr/lib/systemd/system/
Anyway;

# chkconfig --add httpd
# chkconfig httpd on
# chkconfig --list httpd

Note: This output shows SysV services only and does not include native
      systemd services. SysV configuration data might be overridden by native
      systemd configuration.

      If you want to list systemd services use 'systemctl list-unit-files'.
      To see services enabled on particular target use
      'systemctl list-dependencies [target]'.

httpd          	0:off	1:off	2:on	3:on	4:on	5:on	6:off

Its now fixed.