Posted: Sat Jul 12, 2008 5:07 pm
I blame the hiphop.
Page 2 of 2
Posted: Sun Jul 13, 2008 11:50 am
AFAIK bind-chroot is not a requirement for Plesk. They even recommend excluding it from your yum configuration: http://kb.parallels.com/en/234
Posted: Thu Aug 14, 2008 5:52 pm
I had this exact same problem on a RHE4 machine running Plesk 8.1.1. I tried a few different things and had no success. The one thing that fixed the problem was editing the /etc/sysconfig/named file and changing the ROOTDIR="/var/named/run-root" to ROOTDIR="/var/named/chroot".
Tried to start named and didn't get any errors.
I also noticed how all zone files for the sites in /var/named/run-root/var were linked to /var/named/chroot/var/named/run-root/var/
It is working and I am not going to complain.
Tried to start named and didn't get any errors.
I also noticed how all zone files for the sites in /var/named/run-root/var were linked to /var/named/chroot/var/named/run-root/var/
It is working and I am not going to complain.
Posted: Fri Aug 15, 2008 2:20 pm
you can add bind-chroot to exclude list in yum configuration file in linux = than it dont happen again!