Down on the page, you will see the Select NEW Apache version: field. Select from the drop-down list, the Apache configuration you want to build. Click the Next button.
On the next page, enter any additional configuration you need. Click the Start Compiler in Background button. A message will be displayed: Apache Compiler Started in Background. You can monitor Apache rebuild from console using command: tail -f /var/log/apache-rebuild.log . If you are using nginx and/or varnish then you will also need to Rebuild Virtual Hosts!
Wait for a few minutes, go to CWP->Dashboard and look at the Application Version section. You will see there the new Apache version. Also, you will see the message: Message id [5baf75039a0bcce3a1a3be351d7dcb6f]: Apache Re-Build task completed, please check the log for more details.
Select/enter: Enable/Disable – this will enable/disable service monitoring Email notifications to – enter an email address where you will receive notifications Check every – period of time between two checks
Select the Services you want to be monitored.
Click the Submit button. You will see a confirmation message:
Service Monitoring is not enabled
Enabling monitoring in cron
*/15 * * * * root /usr/local/bin/svcMonitor-systemd
Monitoring Enabled: Yes
Notice: If the systemd status of a service is unknown then monitoring will not work for that service.
The selected services that will be monitored are saved in the file /usr/local/etc/services-monitor-systemd
The monitoring cron job can be found in file /etc/cron.d/svcMonitor-systemd
You can manually add/delete services via chkconfig command
chkconfig service_name on
chkconfig service_name off
For example, when enabling all services available we get cron messages like:
Restarted service amavisd.service on cwp1 at Sat Mar 31 01:00:01 EDT 2018 Job for amavisd.service failed because the control process exited with error code. See “systemctl status amavisd.service” and “journalctl -xe” for details.
Restarted service arp-ethers.service on cwp1 at Sat Mar 31 01:00:03 EDT 2018 Restarted service autovt@.service on cwp1 at Sat Mar 31 01:00:04 EDT 2018 Failed to stop autovt@.service: Unit name autovt@.service is missing the instance name.
Restarted service console-shell.service on cwp1 at Sat Mar 31 01:00:05 EDT 2018 Restarted service garb.service on cwp1 at Sat Mar 31 01:00:06 EDT 2018 Restarted service getty@.service on cwp1 at Sat Mar 31 01:00:07 EDT 2018 Failed to stop getty@.service: Unit name getty@.service is missing the instance name.
Restarted service ntalk.service on cwp1 at Sat Mar 31 01:00:09 EDT 2018 Job for ntalk.service failed because a configured resource limit was exceeded. See “systemctl status ntalk.service” and “journalctl -xe” for details.
Restarted service rdisc.service on cwp1 at Sat Mar 31 01:00:10 EDT 2018 Job for rdisc.service failed because the control process exited with error code. See “systemctl status rdisc.service” and “journalctl -xe” for details.
Restarted service svnserve.service on cwp1 at Sat Mar 31 01:00:18 EDT 2018 Job for svnserve.service failed because the control process exited with error code. See “systemctl status svnserve.service” and “journalctl -xe” for details.
Restarted service tcsd.service on cwp1 at Sat Mar 31 01:00:19 EDT 2018 Job for tcsd.service failed because the control process exited with error code. See “systemctl status tcsd.service” and “journalctl -xe” for details.
Restarted service vzfifo.service on cwp1 at Sat Mar 31 01:00:20 EDT 2018
On any web hosting server, it’s very important to be able to easily control the main services, like the Apache server, FTP server etc.
To start/stop/restart & view service statuses in CWP:
Log into CWP as root
On the main page(Dashboard), look for the Services Status section
Here you can see the main services on the server: Apache Webserver, FTP Server, MySQL Database Server, BIND DNS Server, SSH Server, Crontab and the Mail Server Services (Postfix Mail Server, Dovecot IMAP/POP3 Server, ClamAV, AmaVIS, Spam Assassin)
Work with them via the corresponding Start/Stop/Restart/Status buttons.
To configure start-up services go to Services Config->Startup Services. Here you can Enable/Disable the start-up server’ services.
Notice that you can also start/stop/restart/see the status the CWP service. This can be done via the command line with commands: service cwpsrv start; service cwpsrv stop ; service cwpsrv restart ; service cwpsrv status. Output example:
[root@cwp1 ~]# service cwpsrv status
Redirecting to /bin/systemctl status cwpsrv.service
* cwpsrv.service - CentOS Web Panel service (daemon)
Loaded: loaded (/usr/lib/systemd/system/cwpsrv.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2018-03-30 14:29:25 EDT; 12s ago
Process: 12110 ExecStop=/bin/kill -s QUIT $MAINPID (code=exited, status=0/SUCCESS)
Process: 12118 ExecStart=/usr/local/cwpsrv/bin/cwpsrv (code=exited, status=0/SUCCESS)
Process: 12115 ExecStartPre=/usr/local/cwpsrv/bin/cwpsrv -t (code=exited, status=0/SUCCESS)
Main PID: 12119 (cwpsrv)
|-12119 cwpsrv: master process /usr/local/cwpsrv/bin/cwpsrv
|-12120 cwpsrv: worker process
`-12121 cwpsrv: worker process
Mar 30 14:29:25 cwp1 systemd: Starting CentOS Web Panel service (daemon)...
Mar 30 14:29:25 cwp1 cwpsrv: cwpsrv:the configuration file /usr/local/cwpsrv/conf/cwpsrv.conf syntax is ok
Mar 30 14:29:25 cwp1 cwpsrv: cwpsrv:configuration file /usr/local/cwpsrv/conf/cwpsrv.conf test is successful
Mar 30 14:29:25 cwp1 systemd: Failed to read PID from file /usr/local/cwpsrv/var/run/nginx.pid: Invalid argument
Mar 30 14:29:25 cwp1 systemd: Started CentOS Web Panel service (daemon).