Online Interface Connection Reset => Need CPanel/WHM Dependencies

imagenesis

Registered
Aug 2, 2009
1
0
51
Is there a list of CPanel/WHM dependencies? This would be extremely useful in debugging the problem.

Here is my problem:

On Jul28th my WHM and Cpanel online interface stopped working.

I can't access any part of the WHM nterface with firefox but with IE/Chrome I can log in and access the interface but the left side menu and configuration sections display a "The connection was reset error or the equivalent in each browser".

EDIT: I can accomplish the same thing with Firefox as with IE7/Chrome by accessing WHM on port 2086 vs 2087 and on http vs https. Ie http://192.168.0.1:2086 works in Firefox but of course with parts of the interface broken as described above.

For cpanel I can hit the auth in IE7/Chrome but after logging in, there is a connection error in all browsers. I am not able to bring the auth up in firefox.

Cpanel records access in the access logs from both Firefox and IE. There are no errors in the error log.

Also, atleast some of the daemon functions of cpanel remain intact... It restarts httpd at restart and service cpanel restart works.

I have a few questions about what might have broken cpanel...

Can a new version of pcre break cpanel?
Can installing the latest version of postfix break cpanel? As far as I can tell the only postfix dependencies is Berkeley DB...
Can switching selinux from permissive to disabled in the /etc/sysconfig/selinux cause cpanel to break?
Is there a seperate WHM daemon/service?

I think the most useful thing would be to see a list of dependencies and try to find what could have broken it.
 
Last edited:

cPanelDavidG

Technical Product Specialist
Nov 29, 2006
11,212
13
313
Houston, TX
cPanel Access Level
Root Administrator
Is there a list of CPanel/WHM dependencies? This would be extremely useful in debugging the problem.

Here is my problem:

On Jul28th my WHM and Cpanel online interface stopped working.

I can't access any part of the WHM nterface with firefox but with IE/Chrome I can log in and access the interface but the left side menu and configuration sections display a "The connection was reset error or the equivalent in each browser".

EDIT: I can accomplish the same thing with Firefox as with IE7/Chrome by accessing WHM on port 2086 vs 2087 and on http vs https. Ie http://192.168.0.1:2086 works in Firefox but of course with parts of the interface broken as described above.

For cpanel I can hit the auth in IE7/Chrome but after logging in, there is a connection error in all browsers. I am not able to bring the auth up in firefox.

Cpanel records access in the access logs from both Firefox and IE. There are no errors in the error log.

Also, atleast some of the daemon functions of cpanel remain intact... It restarts httpd at restart and service cpanel restart works.

I have a few questions about what might have broken cpanel...

Can a new version of pcre break cpanel?
Can installing the latest version of postfix break cpanel? As far as I can tell the only postfix dependencies is Berkeley DB...
Can switching selinux from permissive to disabled in the /etc/sysconfig/selinux cause cpanel to break?
Is there a seperate WHM daemon/service?

I think the most useful thing would be to see a list of dependencies and try to find what could have broken it.
cPanel/WHM runs as a daemon: cpsrvd which is dependent upon Perl. To ensure all Perl modules that cPanel/WHM relies upon are installed correctly, run the following as root:

/scripts/checkperlmodules

Postfix is not natively supported, so I'm unaware of any adverse interactions between Postfix and cPanel/WHM.

Moving SELinux to disable should actually help cPanel/WHM if anything. We recommend SELinux be disabled when installing cPanel/WHM as SELinux with its default settings will often block access to the cPanel/WHM ports.

If all else fails, run the following via SSH as root:

/scripts/upcp --force

(This is the same thing as going to WHM -> cPanel -> Update to Latest Version and checking the checkbox on that page).

If the issue persists after that is complete, I strongly recommend having our technical analysts take a look at the situation: http://tickets.cPanel.net/submit