Herbert Poetzl wrote: > On Fri, Jul 29, 2011 at 01:46:02PM -0700, Roderick A. Anderson wrote: >> Hate replying to my own post but I got a mostly SOLVED >> solution. Named does start but I still get the message. > >> Ended up copying another guest, added the named files, and ... >> updated bind. > >> I will still have to make a trip to the NOC to reboot the >> system to disable SELinux. > > # echo 0 > /selinux/enforce > > or > > # setenforce 0 Thanks for the suggestions. I tried both along with another two or three others techniques (tricks) I found but none worked. Once I get all the guests updated and the host rebooted I hope it will go away completely. It was my fault for believing the SELinux TUI and not checking the config file. Rod -- > > should do the trick > > best, > Herbert > >> Rod >> -- >> Roderick A. Anderson wrote: >>> I had a major crash of a host (drives in a four drive array) yesterday >>> with limited backups in place. > >>> Got a new system built and am now trying to rebuild all the guests. >>> Every thing has gone rather smoothly until this last guest. > >>> Suddenly I'm getting this error: > >>> Starting named: Error getting active value for named_write_master_zones > >>> CentOS 5.6 host: CentOS guests copied (rsync build) from a older 5.x >>> CentOS system. > >>> Here is vserver-info >>> Versions: >>> Kernel: 2.6.32-131.2.1.el5.vs2.3.0.36.29.6.18.i686 >>> VS-API: 0x00020308 >>> VCI: 0x0000000013011f11 >>> util-vserver: 0.30.216-pre2981; Jun 7 2011, 12:14:10 > >>> Features: >>> CC: gcc, gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-50) >>> CXX: g++, g++ (GCC) 4.1.2 20080704 (Red Hat 4.1.2-50) >>> CPPFLAGS: '' >>> CFLAGS: '-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 >>> -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 >>> -march=i386 -mtune=generic -fasynchronous-unwind-tables -std=c99 -Wall >>> -pedantic -W -funit-at-a-time' >>> CXXFLAGS: '-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 >>> -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m32 >>> -march=i386 -mtune=generic -fasynchronous-unwind-tables -ansi -Wall >>> -pedantic -W -fmessage-length=0 -funit-at-a-time' >>> build/host: i686-redhat-linux-gnu/i686-redhat-linux-gnu >>> Use dietlibc: yes >>> Build C++ programs: yes >>> Build C99 programs: yes >>> Available APIs: v13,net,v21,v22,v23,netv2 >>> ext2fs Source: e2fsprogs >>> syscall(2) invocation: alternative >>> vserver(2) syscall#: 273/glibc >>> crypto api: beecrypt >>> python bindings: yes >>> use library versioning: yes > >>> Paths: >>> prefix: /usr >>> sysconf-Directory: /etc >>> cfg-Directory: /etc/vservers >>> initrd-Directory: /etc/rc.d/init.d >>> pkgstate-Directory: /var/run/vservers >>> vserver-Rootdir: /vservers > >>> I did not get SELinux disabled though I thought I had and all the >>> searches indicate this is a SELinux problem. > >>> I've tried all the methods to disable SELinux without a reboot but to no >>> avail. > >>> I have other guests (rsynced from other remote guests) that are starting >>> bind with the same error. > >>> Any suggestions of what to look at? > > >>> Rod