Can't access WHM/Cpanel
I've been trying to change settings to become pci compliant and managed to lose access to log in to WHM and cpanel and I'm not sure what I did. I'm running a Linux VPS, Nginx Admin, Mariadb, WHM/Cpanel. My host is recommending a WHM/cpanel fresh reinstall but I'll lose my settings. When I run
I get this on the update log.....is there any way to fix this besides a fresh install?
/scripts/upcp -force I get this on the update log.....is there any way to fix this besides a fresh install?
Stopping cPanel ssl services: Waiting for (?^:^(?:stunnel$|stunnel-[0-9\.]+local)) to shutdown ... not running.
[ OK ]
[9064] Can't locate Cpanel.pm in @INC (@INC contains: /usr/local/cpanel /usr/local/cpanel/3rdparty/perl/514/lib/perl5/cpanel_lib/i386-linux-64int /usr/local/cpanel/3rdparty/perl/514/lib/perl5/cpanel_lib /usr/local/cpanel/3rdparty/perl/514/lib/perl5/5.14.4/i386-linux-64int /usr/local/cpanel/3rdparty/perl/514/lib/perl5/5.14.4 /opt/cpanel/perl5/514/site_lib/i386-linux-64int /opt/cpanel/perl5/514/site_lib .) at /usr/local/cpanel/Cpanel/MagicRevision.pm line 12.
[20150227.154332] [9064] BEGIN failed--compilation aborted at /usr/local/cpanel/Cpanel/MagicRevision.pm line 12.
[20150227.154332] [9064] Compilation failed in require at /usr/local/cpanel/Cpanel/Template.pm line 48.
[20150227.154332] [9064] BEGIN failed--compilation aborted at /usr/local/cpanel/Cpanel/Template.pm line 48.
[20150227.154332] [9064] Compilation failed in require at /usr/local/cpanel/scripts/check_valid_server_hostname line 13.
[20150227.154332] [9064] BEGIN failed--compilation aborted at /usr/local/cpanel/scripts/check_valid_server_hostname line 13.
-
I just got this after a forced rei-nstall, fwiw.... ==> SMTP Mail protection has been enabled. [20150227.170749] [21680] All outbound SMTP connections will be redirected to localhost except: [20150227.170749] [21680] uid is root (ports: 25,465,587) [20150227.170749] [21680] uid is cpanel (ports: 25,465,587) [20150227.170749] [21680] gid is mail (ports: 25,465,587) [20150227.170749] [21680] gid is mailman (ports: 25,465,587) [20150227.170749] [21680] Use of uninitialized value in int at /usr/local/cpanel/Cpanel/ServiceManager/Services/Cpsrvd.pm line 54. [20150227.170755] [21680] Waiting for "cpsrvd" to start "" [20150227.170755] [21680] "failed. [20150227.170755] [21680] [20150227.170755] [21680] Service Error [20150227.170755] [21680] The "cpsrvd" service failed to start. [20150227.170755] [21680] [20150227.170755] [21680] Startup Log [20150227.170755] [21680] ==> cpsrvd 11.48.1.2 started [20150227.170755] [21680] ==> cpsrvd: loading security policy....Done [20150227.170755] [21680] ==> cpsrvd: Setting up native SSL support ... Could not load ssl libraries or certificate from /var/cpanel/ssl/cpanel/ at cpsrvd.pl line 702. [20150227.170755] [21680] [20150227.170755] [21680] cpsrvd has failed. Please contact your system administrator if the service does not automagically recover. [20150227.170755] [21680] ==> cPanel TaskQueue Processing Daemon version 1.0 [20150227.170757] [21680] [Fri Feb 27 17:07:56 2015] Starting /usr/local/cpanel/libexec/tailwatch/tailwatchd daemon [20150227.170757] [21680] Log is at /usr/local/cpanel/logs/tailwatchd_log [20150227.170758] [21680] ==> cpdavd: preloaded ssl_write_all! [20150227.170758] [21680] ==> cpdavd: preloaded ssl_write_all! [20150227.170759] [21680] ==> cPanel Log Daemon version 26.0 0 -
I submitted a ticket and they found this....."It ended up being the case that you must have come across something describing one of our workarounds for the recent POODLE SSLv3 vulnerability, as I was able to resolve your issue by moving aside the file used by our temporary workaround to disable SSLv3 in versions where we did not already disable this or allow the administrator to control this, namely the file /var/cpanel/conf/cpsrvd/ssl_socket_args. In any up-to-date and supported version of cPanel, this workaround is not necessary and has in fact been known to cause issues like the one we saw here. Having moved /var/cpanel/conf/cpsrvd/ssl_socket_args aside, cPanel now starts normally." Thanks again to the Cpanel Tech Analysts for solving this one!! 0 -
Hello :) I am happy to see the issue was addressed. Thank you for updating us with the outcome. 0
Please sign in to leave a comment.
Comments
3 comments