Weird cphulkd error after boot ?

[nyjimbo]

One of our machines started spewing errors that it was getting timeout errors on the NIC and then we couldnt get in or out of the box with anything.

Booting it brought it back up but then we saw :

Jun 5 15:17:13 xxxxx PAM-hulk[2136]: timeout while connecting to cphulkd
Jun 5 15:17:13 xxxxx PAM-hulk[2136]: error reading welcome from stream socket
Jun 5 15:17:31 xxxxx PAM-hulk[2136]: timeout while connecting to cphulkd
Jun 5 15:17:31 xxxxx PAM-hulk[2136]: error reading welcome from stream socket

until we unplugged the ethernet cable, waited a minute or so and then plugged it back in.

Anyone see this error before or know what it means ?

 

[a_raims]

I am also facing a similar issue. Named crashed and this is what the logs says:
====
PAM-hulk[16013]: failed to connect stream socket
named[22305]: shutting down: flushing changes
named[22305]: stopping command channel on 127.0.0.1#953
=====

 

[zenkis]

Same issue here!

 

[Miraenda]

Actually, the original issue and thread is about cPHulkd errors, while named not starting up is an entirely different matter. Have you tried to restart named again to see the results?

/etc/init.d/named restart

When doing that restart, please have a second window open in root SSH and tail /var/log/messages to see what it shows on the restart (if it fails) so you can see what errors are being logged for why it isn't starting.

You can also try this command to see if any domains in /etc/named.conf file are causing named to refuse to start (missing /var/named/domain.com.db files or duplicate domains in /etc/named.conf will cause it to fail to load):

/usr/sbin/named-checkconf -z /etc/named.conf > /dev/null

There might also be a log for named at /var/run/named that might show additional information if it is failing.

I really don't know if you are experiencing named issues or cPHulkd ones given the thread has two different topics being discussed, so please clarify if it isn't named and is indeed cPHulkd as the issue here.