Anyone having this updater problem?

[lyew]

Hi,

Over the last two days, the cpanel/whm updates just haven't been going smoothly. I keep getting this in my email. Is anyone else experiencing this?

PHP version file is up to date
Cpanel updates are coming from layer2.cpanel.net Checking /dev/hda....OK Checking /dev/hdc....OK x - creating lock directory x - SKIPPING /usr/local/lib/php.ini (file already exists) Using Mysql4 Using RPM Backend: RPM version 4.1 Fetching rpm updates list...Unable to retrieve file Died at /scripts/HTTPreq.pm line 12.
Using RPM Backend: RPM version 4.1
Fetching rpm updates list...Done

gzip: /root/.cpupdates/3-2-2004.updates.gz: unexpected end of file Cannot fetch rpm updates list at /scripts/cPanelRPM.pm line 154.
Done

gzip: /root/.cpupdates/3-2-2004.updates.gz: unexpected end of file Cannot fetch rpm updates list at /scripts/cPanelRPM.pm line 154.
rsync: getaddrinfo: rsync.cpanel.net 873: Temporary failure in name resolution rsync error: error in socket IO (code 10) at clientserver.c(83) Bad arg length for Socket::pack_sockaddr_in, length is 0, should be 4 at /usr/lib/perl5/5.8.0/i386-linux-thread-multi/Socket.pm line 373.

 

[Tom Pyles]

I'm getting them as well on one of our servers....still looking into it.

 

[rcthost]

I have that exact error too. Also BIND failed and will not start. I am assuming they are both related.

Please let me know if you find anything out about this. Thanks!

 

[rcthost]

I solved my problem. In case it helps anyone I ran named-checkconf /etc/named.conf which showed a duplicate zone. Removed the zone, restarted bind and all is ok now.

 

[Tom Pyles]

Originally posted by rcthost
I solved my problem. In case it helps anyone I ran named-checkconf /etc/named.conf which showed a duplicate zone. Removed the zone, restarted bind and all is ok now.

My fix was something similar, except my error was in /etc/resolv.conf

As soon as I corrected it, things started working.

 

[lyew]

Funny, two days later, after not having done anything, CPanel is now updating properly. I'll have to wait a couple of hours to see if it is still working today.