Hi there (especially Daniel),
the 127.0.0.1 problem on CentOS vs2.3.0.27.1 with 127.0.0.1 binding of
guests still exists:
Have set up a new CO5 guest for nameservices, which (by default
package of centos) binds rndc to 127.0.0.1#953, as per error message:
| # service named status
| rndc: connect failed: 127.0.0.1#953: operation canceled
If not cancelling, it hangs "forever". Same on "vserver stop" on host
- this kills the process after quite a long time hanging on "stopping
named".
System info:
CentOS 5 host w/kernel 2.6.22.9-vs2.3.0.27.1 (dhozac repository) on an
Opteron875 Single-CPU system with recent CO5 updates installed,
util-vserver-core-0.30.214-1.1.el5.centos
util-vserver-sysv-0.30.214-1.1.el5.centos
util-vserver-lib-0.30.214-1.1.el5.centos
util-vserver-0.30.214-1.1.el5.centos
Guest is plain CentOS 5 system with recent updates and
bind-9.3.3-9.0.1.el5 for nameservice.
Both previous guesses of nflags did not work:
# echo ~HIDE_LBACK >> /etc/vservers/[VSname]/nflags
# echo ~SINGLE_IP >> /etc/vservers/[VSname]/nflags
None of the 4 possible variants of a/m flags beeing un/set changed any
of the behaviour.
Ideas?
--
regards 'n greez,
Guenther Fuchs
(aka "muh" and "powerfox")