Not 100% sure at this point but some servers are having DNS break tonight after a UPCP running. The only thing we have narrowed it down to at this point is having RHEL 3 and cPanel on the box. When UPCP runs it breaks named and stops it from responding to anything. The fix is simple just do:
up2date -u bind-libs
service named restart
That should be it =-)
not working for me
I have the same problem, but it's not working for me :(
getting following
getting following error in up2date -u bind
error: unpacking of archive failed on file /usr/bin/dig: cpio: rename
There was a fatal RPM install error. The message was:
There was a rpm unpack error installing the package: bind-utils-9.2.4-14_EL3
# /scripts/restartsrv named
Waiting for named to restart..............finished.
named has failed, please contact the sysadmin (result was "named is not running").
Jul 23 08:04:34 svr1 named: named shutdown failed
Jul 23 08:04:34 svr1 named[3992]: starting BIND 9.2.4 -u named
Jul 23 08:04:34 svr1 named[3992]: using 4 CPUs
Jul 23 08:04:34 svr1 named[3992]: loading configuration from '/etc/named.conf'
Jul 23 08:04:34 svr1 named[3992]: no IPv6 interfaces found
Jul 23 08:04:34 svr1 named[3992]: listening on IPv4 interface lo, 127.0.0.1#53
Jul 23 08:04:34 svr1 named[3992]: listening on IPv4 interface eth0, 67.15.202.16#53
Jul 23 08:04:34 svr1 named[3992]: listening on IPv4 interface eth0:1, 67.15.202.202#53
Jul 23 08:04:34 svr1 named[3992]: listening on IPv4 interface eth0:2, 67.15.202.114#53
Jul 23 08:04:34 svr1 named[3992]: listening on IPv4 interface eth0:3, 67.15.202.115#53
Jul 23 08:04:34 svr1 named: named startup succeeded
Jul 23 08:04:34 svr1 named[3992]: zone version.bind/CH: has 0 SOA records
Jul 23 08:04:34 svr1 named[3992]: zone version.bind/CH: has no NS records
Jul 23 08:04:34 svr1 named[3992]: view.c:347: REQUIRE((&view->references)->refs > 0) failed
Jul 23 08:04:34 svr1 named[3992]: exiting (due to assertion failure)
bind
Looks like the rpm install failed somehow so you need to look into that.
Make sure you are running rhel3 and not 4, also make sure the versions look correct.
problem solved... "The RFX
problem solved...
"The RFX LES is a tool wich change chmod and chattr of many system files, is powerfull for improve security of systems !!!"
I had to chattr -i /usr/bin/dig in order to run up2date
LES
Yeah that would do it ;) I believe in the documents it says that it will break that. I generally use every option in LES but that on.