cpanel_ccs Service down and not launching
I think I've narrowed down the issue, which I've bolded, but everytime I try to run restartsrv_cpanel_ccs, the following error occurs.
[QUOTE]
Waiting for "cpanel_ccs" to start ""info [restartsrv_cpanel_ccs] systemd failed to start the service "cpanel-ccs" (The "/usr/bin/systemctl restart cpanel-ccs.service --no-ask-password" command (process 5752) reported error number 1 when it ended.): Job for cpanel-ccs.service failed because the control process exited with error code. See "systemctl status cpanel-ccs.service" and "journalctl -xe" for details.
"info [restartsrv_cpanel_ccs] systemd failed to start the service "cpanel-ccs" (The "/usr/bin/systemctl restart cpanel-ccs.service --no-ask-password" command (process 5849) reportederror number 1 when it ended.): Job for cpanel-ccs.service failed because the control process exited with error code. See "systemctl status cpanel-ccs.service" and "journalctl -xe" for details.
"failed.
Cpanel::Exception::Services::StartError
Service Status
Service Error
(XID wswqby) The "cpanel_ccs" service failed to start.
Startup Log
Feb 20 09:11:48 ... systemd[1]: Starting Apple Calendar Server...
Feb 20 09:11:48 ... run[5850]: Using /opt/cpanel-ccs/.develop/virtualenv/bin/python as Python
Feb 20 09:11:48 ... run[5850]: Starting server...
Feb 20 09:11:50 ... run[5850]: Reading configuration from file: /opt/cpanel-ccs/conf/caldavd-dev.plist
Feb 20 09:11:50 ... run[5850]: Pidfile /opt/cpanel-ccs/data/Logs/state/caldavd.pid contains non-numeric value
Feb 20 09:11:50 ... systemd[1]: cpanel-ccs.service: control process exited, code=exited status=1
Feb 20 09:11:50 ... systemd[1]: Failed to start Apple Calendar Server.
Feb 20 09:11:50 ... systemd[1]: Unit cpanel-ccs.service entered failed state.
Feb 20 09:11:50 ... systemd[1]: cpanel-ccs.service failed.
cpanel_ccs has failed. Contact your system administrator if the service does not automagically recover.
I believe the issue is with the Apple Calendar Server, but I can't find any help online with that issue.
I believe the issue is with the Apple Calendar Server, but I can't find any help online with that issue.
-
Also to add, I do have installed the Calendar and Contacts Server [experimental] plugin. Version: 9.2.a-49.1. 0 -
We have the same problem since an update to version 9.2.a-49.1 0 -
Same problem and how to recover: I ran /usr/local/cpanel/scripts/restartsrv_cpanel_ccs It did not recover, then I saw the next line in between the information that apears in the screen: curl: (7) Failed connect to sourceware.org:21; Connection refused I ping sourceware.org with result ip address: 209.132.180.131 I white listed the IP address in the firewall then I ran again /usr/local/cpanel/scripts/restartsrv_cpanel_ccs Done, it recovered. Hope this help. 0 -
I white listed the IP address in the firewall then I ran again /usr/local/cpanel/scripts/restartsrv_cpanel_ccs
I just now tried this, whitelisting within ConfigServer Firewall, still no luck when trying to run the command after.0 -
Same problem. Service Name cpanel-ccs Service Status failed ? Notification The service "cpanel-ccs" appears to be down. Service Check Method The system"s command to check or to restart this service failed. Number of Restart Attempts 210 Service Check Raw Output (XID sqsxsg) The "cpanel_ccs" service is down. The subprocess "/usr/local/cpanel/scripts/restartsrv_cpanel_ccs" reported error number 255 when it ended. Startup Log Feb 21 18:11:35 systemd[1]: Starting Apple Calendar Server... Feb 21 18:11:35 run[30883]: Using /opt/cpanel-ccs/.develop/virtualenv/bin/python as Python Feb 21 18:11:35 run[30883]: Starting server... Feb 21 18:11:38 run[30883]: Reading configuration from file: /opt/cpanel-ccs/conf/caldavd-dev.plist Feb 21 18:11:38 run[30883]: Pidfile /opt/cpanel-ccs/data/Logs/state/caldavd.pid contains non-numeric value Feb 21 18:11:38.systemd[1]: cpanel-ccs.service: control process exited, code=exited status=1 Feb 21 18:11:38 .systemd[1]: Failed to start Apple Calendar Server. Feb 21 18:11:38 .systemd[1]: Unit cpanel-ccs.service entered failed state. Feb 21 18:11:38 systemd[1]: cpanel-ccs.service failed. 0 -
Do you guys that have cpanel_ccs failed and not able to be restarted have anything logged to the following logs? /usr/local/cpanel/logs/error_log
/var/log/lfd.log
/var/log/messages
Also, please keep in mind this is an experimental plugin and could suffer from unexpected/unpredictable behavior0 -
Do you guys that have cpanel_ccs failed and not able to be restarted have anything logged to the following logs?
/usr/local/cpanel/logs/error_log
/var/log/lfd.log
/var/log/messages
Also, please keep in mind this is an experimental plugin and could suffer from unexpected/unpredictable behavior
/usr/local/cpanel/logs/error_log[2020-02-22 00:57:20 +0200] info [cpsrvd] version 11.86.0.4 online [2020-02-22 01:00:19 +0200]: "/usr/local/cpanel/scripts/restartsrv_unknown cpanel-ccs" called by (1045 - tailwatc$ [2020-02-22 01:00:24 +0200] info [queueprocd] chkservd::Notify Notification => @gmai***** via EMAIL [eve$ [2020-02-22 01:00:27 +0200] info [restartsrv_unknown] systemd failed to start the service "cpanel-ccs" (The "/usr$ [2020-02-22 01:00:36 +0200] info [restartsrv_unknown] systemd failed to start the service "cpanel-ccs" (The "/usr$ [2020-02-22 01:06:18 +0200]: "/usr/local/cpanel/scripts/restartsrv_unknown cpanel-ccs" called by (2248 - tailwatc$ [2020-02-22 01:06:22 +0200] info [restartsrv_unknown] systemd failed to start the service "cpanel-ccs" (The "/usr$ [2020-02-22 01:06:22 +0200] info [queueprocd] chkservd::Notify Notification => @gmai***** via EMAIL [eve$ [2020-02-22 01:06:31 +0200] info [restartsrv_unknown] systemd failed to start the service "cpanel-ccs" (The "/usr$
/var/log/lfd.logFeb 22 00:00:04 server lfd[19369]: Account Tracking... Feb 22 00:00:04 server lfd[19369]: SSH Tracking... Feb 22 00:00:04 server lfd[19369]: Webmin Tracking... Feb 22 00:00:04 server lfd[19369]: SU Tracking... Feb 22 00:00:04 server lfd[19369]: Console Tracking... Feb 22 00:00:04 server lfd[19369]: WHM Tracking... Feb 22 00:00:04 server lfd[19369]: Watching /var/log/secure... Feb 22 00:00:04 server lfd[19369]: Watching /var/log/exim_mainlog... Feb 22 00:00:04 server lfd[19369]: Watching /usr/local/cpanel/logs/login_log... Feb 22 00:00:04 server lfd[19369]: Watching /var/log/maillog... Feb 22 00:00:04 server lfd[19369]: Watching /etc/apache2/logs/error_log... Feb 22 00:00:04 server lfd[19369]: Watching /var/log/messages... Feb 22 00:00:04 server lfd[19369]: Watching /var/log/customlog... Feb 22 00:00:04 server lfd[19369]: Watching /usr/local/cpanel/logs/access_log... Feb 22 00:34:12 server lfd[27918]: (smtpauth) Failed SMTP AUTH login from 193.56.28.242 (PL/Poland/-): 5 in the l$ Feb 22 01:06:14 server lfd[2147]: *WHM/cPanel root access
/var/log/messagesFeb 22 01:15:05 server systemd: Removed slice User Slice of root. Feb 22 01:15:09 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:15:13 server systemd: Removed slice User Slice of munin. Feb 22 01:15:18 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:15:18 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:30:af:08$ Feb 22 01:15:29 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:15:42 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:30:af:08$ Feb 22 01:15:44 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:15:44 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:15:44 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:15:55 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:15:59 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:30:af:08$ Feb 22 01:16:05 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:16:10 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:30:af:08$ Feb 22 01:16:14 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:16:26 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:16:30 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$ Feb 22 01:16:31 server kernel: Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC=00:50:56:3c:ee:b1:28:99:3a:4d:23:91:08$0 -
@HaNi Ghaith The cPanel error log output is cutoff can you readd that? 0 -
Hello, I opened a ticket and got the following response, which explained and solved the problem: Feb 24 17:57:21 server.domain.com run[4725]: Pidfile /opt/cpanel-ccs/data/Logs/state/caldavd.pid contains non-numeric value It looks like this was due to the caldavd.pid file being 0 bytes in size. To resolve the issue, I restarted the cpdavd service, moved aside the empty pid file, and then was able to successfully start the cpanel_ccs service: [17:58:13 server root@93454157 ~]cPs# /scripts/restartsrv_cpdavd --restart Waiting for "cpdavd" to restart gracefully ""waiting for "cpdavd" to initialize "finished. Service Status cpdavd (cpdavd - accepting connections on: 2077, 2078 (dormant)) is running as root with PID 3011 (systemd+/proc check method). Startup Log Feb 20 20:20:26 server.domain.com systemd[1]: Starting cPanel dav services... Feb 20 20:20:27 server.domain.com systemd[1]: Can't open PID file /var/run/cpdavd.pid (yet?) after start: No such file or directory Feb 20 20:20:27 server.domain.com systemd[1]: Started cPanel dav services. cpdavd restarted successfully. [17:58:17 server root@93454157 ~]cPs# mv -v /opt/cpanel-ccs/data/Logs/state/caldavd.pid{,-bak} "/opt/cpanel-ccs/data/Logs/state/caldavd.pid" -> "/opt/cpanel-ccs/data/Logs/state/caldavd.pid-bak" [17:58:26 server root@93454157 ~]cPs# /scripts/restartsrv_cpanel_ccs --start Waiting for "cpanel_ccs" to start ""waiting for "cpanel_ccs" to initialize "finished. Service Status cpanel-ccs (CalendarServer 9.2.a+fbd0e11675cc0f64a425581b5c8398cc1e09cb6a [Combined] ) is running as cpanel-ccs with PID 5128 (systemd+/proc check method). cpanel-ccs (/usr/bin/pg_ctl start --log=/opt/cpanel-ccs/data/Logs/postgres.log --timeout=86400 -w -o -c listen_addresses='' -c unix_socket_directories=/opt/cpanel-ccs/data/Data/Database/psqlsocks -c shared_buffers=139 -c max_connections=93 -c standard_conforming_strings=on -c unix_socket_permissions=0770 -c log_line_prefix=%t) is running as cpanel-ccs with PID 5129 (systemd+/proc check method). Startup Log Feb 24 17:58:33 server.domain.com systemd[1]: Starting Apple Calendar Server... Feb 24 17:58:34 server.domain.com run[5036]: Using /opt/cpanel-ccs/.develop/virtualenv/bin/python as Python Feb 24 17:58:34 server.domain.com run[5036]: Starting server... Feb 24 17:58:36 server.domain.com systemd[1]: Started Apple Calendar Server. cpanel_ccs started successfully. 0 -
Glad to see your issue was able to be resolved. Thank you for updating here. 0 -
Do you guys that have cpanel_ccs failed and not able to be restarted have anything logged to the following logs?
/usr/local/cpanel/logs/error_log
/var/log/lfd.log
/var/log/messages
Also, please keep in mind this is an experimental plugin and could suffer from unexpected/unpredictable behavior
Hey Lauren, see below for the results from/usr/local/cpanel/logs/error_log
[QUOTE][2020-02-24 20:14:34 -0500]: "/usr/local/cpanel/scripts/restartsrv_cpanel_ccs " called by (10000 - /bin/bash -l) [2020-02-24 20:14:37 -0500] info [restartsrv_cpanel_ccs] systemd failed to start the service "cpanel-ccs" (The "/usr/bin/systemctl restart cpanel-ccs.service --no-ask-password" command (process 10040) reported error number 1 when it ended.): Job for cpanel-ccs.service failed because the control process exited with error code. See "systemctl status cpanel-ccs.service" and "journalctl -xe" for details. [2020-02-24 20:14:45 -0500] info [restartsrv_cpanel_ccs] systemd failed to start the service "cpanel-ccs" (The "usr/bin/systemctl restart cpanel-ccs.service --no-ask-password" command (process 10130) reported error number 1 when it ended.): Job for cpanel-ccs.service failed because the control process exited with error code. See "systemctl status cpanel-ccs.service" and "journalctl -xe" for details.
Nothing out of the ordinary for the other files you mentioned is there something I should be looking for? Here is the results when I run the systemctl status command: [QUOTE]cpanel-ccs.service - Apple Calendar Server Loaded: loaded (/etc/systemd/system/cpanel-ccs.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2020-02-24 20:26:36 EST; 7s ago Process: 11774 ExecStart=/opt/cpanel-ccs/bin/run -dn (code=exited, status=1/FAILURE) Feb 24 20:26:34 ... systemd[1]: Starting Apple Calendar Server... Feb 24 20:26:34 ... run[11774]: Using /opt/cpanel-ccs/.develop/virtualenv/bin/python as Python Feb 24 20:26:34 ... run[11774]: Starting server... Feb 24 20:26:36 ... run[11774]: Reading configuration from file: /opt/cpanel-ccs/conf/caldavd-dev.plist Feb 24 20:26:36 ... run[11774]: Pidfile /opt/cpanel-ccs/data/Logs/state/caldavd.pid contains non-...value Feb 24 20:26:36 ... systemd[1]: cpanel-ccs.service: control process exited, code=exited status=1 Feb 24 20:26:36 ... systemd[1]: Failed to start Apple Calendar Server. Feb 24 20:26:36 ... systemd[1]: Unit cpanel-ccs.service entered failed state. Feb 24 20:26:36 ... systemd[1]: cpanel-ccs.service failed. Hint: Some lines were ellipsized, use -l to show in full.
Which still leads me nowhere.0 -
Finally all worked out! After the latest update I ended up having the same issue that HaNi Ghaith had. So once I did his fix now the service started successfully. 0 -
Finally all worked out! After the latest update I ended up having the same issue that HaNi Ghaith had. So once I did his fix now the service started successfully.
I feel happy to hear this news.0 -
No luck here. I did everything recommended so far, but nothing. And I cannot post my log here, it says Oops! We ran into some problems. Please try again later. More error details may be in the browser console. So twice no luck. 0
Please sign in to leave a comment.
Comments
14 comments