From: Adrian Reyer (are_at_lihas.de)
Date: Wed 22 Dec 2004 - 08:59:36 GMT
it gets increasingly strange with /proc here.
The first symptoms had been for me to be unable to access /proc/net
(e.g. ifconfig) from the master server. Now I have enabled
and am able to see with e.g. dmesg what happens:
vxW: xid=0 did lookup hidden 00000101fc438058[#106,4026531861] »/proc/net«.
It looks to me like #106 is a contextid, and indeed, if I 'vserver
enter' that server, I have a working ifconfig and can access
/proc/net. I have no idea how to give /proc/net back to xid 0 or why
it gets messed up.
However, xid of /proc/net at least remains the same. If I stop the
vservers, I see this about /proc/meminfo in my log:
Dec 22 09:43:11 localhost kernel: vxW: xid=106 did lookup hidden 00000101ffdf8b98[#103,4026531842] <BB>/proc/meminfo<AB>.
Dec 22 09:43:11 localhost kernel: vxW: xid=103 did lookup hidden 00000101f0e2add8[#101,4026531842] <BB>/proc/meminfo<AB>.
Dec 22 09:43:11 localhost kernel: vxW: xid=104 did lookup hidden 00000101f0e2add8[#103,4026531842] <BB>/proc/meminfo<AB>.
Dec 22 09:43:13 localhost kernel: vxW: xid=101 did lookup hidden 00000101f6c02dd8[#102,4026531842] <BB>/proc/meminfo<AB>.
It looks to me like /proc/meminfo has always the wrong xid for the
processes accessing it and always different ones.
Anyone with a hint here?
-- LiHAS - LinuxHaus Stuttgart Fon: +49 (7 11) 2 85 19 05 Inh.: Adrian Reyer Fax: +49 (7 11) 5 78 06 92 Mail: lihas_at_lihas.de Linux, Netzwerke, Consulting & Support http://lihas.de/ _______________________________________________ Vserver mailing list Vserver_at_list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver