Re: [Vserver] I'm in trouble now ....
[EMAIL PROTECTED] (Paul S. Gumerman) writes: Ran vserver fc3-reference hashify, which ran ok with one message (sorry, can't recall it now). The exact message would be helpful perhaps. Then tried vserver loco-reference hashify which failed with a message saying vserver ... suexec is support for running vserver only; aborting ... *BTW, that should read supported.* Thx, speling has been fixed. When this message appears, 'vhashify' stopped at a very early stage without modifying any file. I tried to start loco-reference, but got the message an error occurred very likely that initscript faild with no other details regarding just what had failed. When I started it again, I did get the message that lines 1 and 3 in the fstab had failed because the fs's were already mounted, so it did get that far, at least. I also found that I could no longer stop any of the running vservers. The message was still running unexpectedly. Please investigate it manually. Running vserver-stat results in a Segmentaion fault. Tracking this segfault would be helpfully. Do you see kernel messages (oops) there? Else, possible ways to trace it are: * chcontext --xid 1 strace vserver-stat * chcontext --xid 1 gdb vserver-stat -- r + bt (perhaps compiling tools with 'CFLAGS=-O0 -g3 ./configure ...') Also, this might be a hint: if I try running vtop (as root) I get chcontext: execvp: (top) Permission denied mmh... is SELinux enabled? Enrico pgpSm03zpuTQh.pgp Description: PGP signature ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] I'm in trouble now ....
Enrico --- thanks for the quick help.
The kernel is compiled with SELINUX, but also compiled with SELINUX
disabled.
The thing is, this was all working fine a short time ago; I'm
completely boggled! Should I recompile with those CFLAGS next, or what?
Enrico Scholz wrote:
[EMAIL PROTECTED] ("Paul S. Gumerman") writes:
I tried to start loco-reference, but got the message "an error
occurred very likely that initscript faild " with no other
details regarding just what had failed. When I started it again, I did
get the message that lines 1 and 3 in the fstab had failed because the
fs's were already mounted, so it did get that far, at least.
I also found that I could no longer stop any of the running vservers.
The message was " still running unexpectedly. Please investigate
it manually."
Running vserver-stat results in a Segmentaion fault.
Tracking this segfault would be helpfully. Do you see kernel messages
(oops) there? Else, possible ways to trace it are:
* chcontext --xid 1 strace vserver-stat
* chcontext --xid 1 gdb vserver-stat -- r + bt
I tried these two ...
[EMAIL PROTECTED] ~]# chcontext --xid 1 strace vserver-stat
New security context is 1
chcontext: execvp("strace"): Permission denied
[EMAIL PROTECTED] ~]# chcontext --xid 1 gdb vserver-stat -- r + bt
chcontext: execvp("gdb"): Permission denied
[EMAIL PROTECTED] ~]#
Ran "vserver fc3-reference hashify", which ran ok with one message
(sorry, can't recall it now).
The exact message would be helpful perhaps.
I know, I know ... sorry, but it only did it the one time, now I just
get the "vserver ...
suexec" message. But obviously something bigger than just vhashify
problems is happening here, so I'm not too concerned about this point
at the moment.
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] I'm in trouble now ....
On Mon, Mar 28, 2005 at 09:09:01AM -0500, Paul S. Gumerman wrote: Enrico --- thanks for the quick help. The kernel is compiled with SELINUX, but also compiled with SELINUX disabled. The thing is, this was all working fine a short time ago; I'm completely boggled! Should I recompile with those CFLAGS next, or what? Enrico Scholz wrote: [EMAIL PROTECTED] (Paul S. Gumerman) writes: I tried to start loco-reference, but got the message an error occurred very likely that initscript faild with no other details regarding just what had failed. When I started it again, I did get the message that lines 1 and 3 in the fstab had failed because the fs's were already mounted, so it did get that far, at least. I also found that I could no longer stop any of the running vservers. The message was still running unexpectedly. Please investigate it manually. Running vserver-stat results in a Segmentaion fault. Tracking this segfault would be helpfully. Do you see kernel messages (oops) there? Else, possible ways to trace it are: * chcontext --xid 1 strace vserver-stat * chcontext --xid 1 gdb vserver-stat -- r + bt I tried these two ... [EMAIL PROTECTED] ~]# chcontext --xid 1 strace vserver-stat New security context is 1 chcontext: execvp(strace): Permission denied [EMAIL PROTECTED] ~]# chcontext --xid 1 gdb vserver-stat -- r + bt chcontext: execvp(gdb): Permission denied [EMAIL PROTECTED] ~]# Ran vserver fc3-reference hashify, which ran ok with one message (sorry, can't recall it now). The exact message would be helpful perhaps. I know, I know ... sorry, but it only did it the one time, now I just get the vserver ... suexec message. But obviously something bigger than just vhashify problems is happening here, so I'm not too concerned about this point at the moment. please give the testme.sh script (version 0.11) a try (http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh) and pay a visit to the irc channel if possible, we can try to narrow down the issue there much easier than via email ... TIA, Herbert ___ Vserver mailing list [EMAIL PROTECTED] [3]http://list.linux-vserver.org/mailman/listinfo/vserver References 1. mailto:[EMAIL PROTECTED] 2. mailto:Vserver@list.linux-vserver.org 3. http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] I'm in trouble now ....
On Mon, Mar 28, 2005 at 06:36:39PM +0200, Herbert Poetzl wrote: On Mon, Mar 28, 2005 at 09:09:01AM -0500, Paul S. Gumerman wrote: [all the funny details zapped] please give the testme.sh script (version 0.11) a try (http://vserver.13thfloor.at/Stuff/SCRIPT/testme.sh) Linux-VServer Test [V0.11] (C) 2003-2005 H.Poetzl chcontext: execvp(grep): Permission denied chcontext failed! New security context is 1 chbind failed! Linux 2.6.11-rc3-vs1.9.4-rc4drbd x86_64/0.30.205/0.30.205 [Ea] VCI: 0001:0025 236 and pay a visit to the irc channel if possible, we can try to narrow down the issue there much easier than via email ... did work out as expected, we did discover that dietlibc 0.28 (and probably earlier too) is broken one fc3/x86_64 ... best, Herbert ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
[Vserver] I'm in trouble now ....
Herbert ... hope you can help. Here's what's happened:
I've had 1.94-rc4 with kernel 2.6.11-rc3 running just fine on a dual
Opteron box under FC3-x86_64. I have two vservers that I startup on
reboot, and two more "reference" servers that were startable. These
are all FC3-x86_64 vservers.
Thursday, I did a "yum update", and got 18 packages updated. Then I
downloaded vserver-util-0.30.205 (I was REALLY excited to read about
vhashify, and wanted to try it), found an updated dietlibc-0.28
(previous version would not build on x86_64), built and installed that,
then built and installed util-vserver.
Ran "vserver fc3-reference hashify", which ran ok with one message
(sorry, can't recall it now).
Then tried "vserver loco-reference hashify" which failed with a message
saying "vserver ... suexec is support for running vserver only;
aborting ..." BTW, that should read "supported".
I tried to start loco-reference, but got the message "an error occurred
very likely that initscript faild " with no other details
regarding just what had failed. When I started it again, I did get the
message that lines 1 and 3 in the fstab had failed because the fs's
were already mounted, so it did get that far, at least.
I also found that I could no longer stop any of the running vservers.
The message was " still running unexpectedly. Please investigate
it manually."
Running vserver-stat results in a Segmentaion fault.
I tried going back to util-vserver-0.30.203 ... didn't change
anything. I tried linking with glibc ... again no change. I tried
rebooting ... no change.
One interesting thing ... the two vservers that are set up to start on
boot still start! (Which is a very good thing, since my development
database in now running in one of those vservers.)
Also, this might be a hint: if I try running vtop (as root) I get
"chcontext: execvp: ("top") Permission denied"
I also just noticed that the attempt to hashify, after the reboot, now
also says "failed to determine configfiles".
ARRRGGGHHH!
Let me know if there's any more info that I can provide
Hopefully,
Paul
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
