Hi Herbert,
Been too long since I've been playing with kernel oops :(. I started to
write down the Oops screen and got too tired too quickly and missed
getting enough info. What happen to it being trapped in
/var/log/ ? I use to just run ksymoops on that and get what was
needed. Anyhow, for no
[EMAIL PROTECTED] writes:
> vserver test enter
> ipv4root is now 194.239.210.107
> Can't set the new security context
> : Invalid argument
Try the 0.24.90 release candidate which is available at
http://savannah.nongnu.org/files/?group=util-vserver
Enrico
__
On Mon, Nov 17, 2003 at 10:35:39PM +0100, [EMAIL PROTECTED] wrote:
> i just compiled and installed vserver 1.1.3 and i do have some trouble.
> When i do a vps -e i can see it is running, but i cant enter it
>
> vserver test enter
> ipv4root is now 194.239.210.107
> Can't set the new security conte
[EMAIL PROTECTED] ("Allen D. Parker II") writes:
> I'm no programmer, but I do believe, it would be pretty nice if the
> "owner" of a context (fake "root" user) could halt/reboot *their*
> vserver via /sbin/init, /sbin/reboot or /sbin/halt. It'd be nice to
> have a way to pass messages *securely*
i just compiled and installed vserver 1.1.3 and i do have some trouble.
When i do a vps -e i can see it is running, but i cant enter it
vserver test enter
ipv4root is now 194.239.210.107
Can't set the new security context
: Invalid argument
test.conf
-
S_HOSTNAME="test"
IPROOT="eth0"
ONBO
On Mon, 2003-11-17 at 20:00, [EMAIL PROTECTED] wrote:
> The e-mail you have sent to this domain (qlusters.com) did not reach its indended
> destination.
> Possible reasons: the e-mail address entered is mispelled or the user is none
> existant.
>
> Note:
> -
> You may see the original e-
Hi Bertl and others. As agreed i tested binding to specific ip adresses on
my machine
Linux pony 2.4.21-vs1.00 #2 SMP Mon Nov 3 18:30:51 CET 2003 i586 unknown
i tested using sshd, and telling it to bind to a specific listen address.
It refused to bind to any specific ip unless that vserver had tha
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
On Mon, Nov 17, 2003 at 05:36:03PM +0100, Herbert Poetzl wrote:
> On Mon, Nov 17, 2003 at 04:02:58PM +, [EMAIL PROTECTED] wrote:
> > Hi,
> >
> > I have an idea that would be nice to try and could
> > also be a useful test of our administration tools.
> >
> > We create a virtual server and aut
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
UML looks working..
(none):~# chcontext --ctx 100 grep context /proc/self/status
New security context is 100
s_context: 100 [ 100]
__NR_new_s_context: 273
(none):~# chbind --ip 192.168.0.42 false
ipv4root is now 192.168.0.42
(none):~# chcontext --secure --ctx 100 mknod /tmp/x c 0 0
New security co
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
On Mon, 17 Nov 2003, Matt Ayres wrote:
> You're correct, we observed the same thing. The CPU/Load is caused by
> kswapd. Errors exactly like this has been reported for 2.4.2 and 2.4.9
> (that we can find), so perhaps one of the bugs re-surfaced in 2.4.2X.
After a bit of hunting I also found the
On Mon, 2003-11-17 at 12:45, Martin Josefsson wrote:
> On Mon, 2003-11-17 at 12:23, Matt Ayres wrote:
> I've seen this one on a few diffrent systems, even servers at kernel.org
> has seen this exact problem but noone has been able to reproduce it at
> will or trace it, the machines seem to "half-
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
Mark,
You're correct, we observed the same thing. The CPU/Load is caused by
kswapd. Errors exactly like this has been reported for 2.4.2 and 2.4.9
(that we can find), so perhaps one of the bugs re-surfaced in 2.4.2X.
We've tried this with and without Herbert's rmap15k patches. Slightly
differen
On Mon, Nov 17, 2003 at 05:34:28PM +, Holger Rabbach wrote:
> Hi,
>
> >The e-mail you have sent to this domain (qlusters.com) did not reach its
> >indended destination.
> >Possible reasons: the e-mail address entered is mispelled or the user is
> >none existant.
>
> am I the only one gettin
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
On Mon, 2003-11-17 at 12:23, Matt Ayres wrote:
> I have 2 servers who keep crashing, sometimes every few hours... I am
> still working on a console solution so I don't know the exact place
> where the problem is.
>
> The servers are in a "half hung" state, they respond to PING and will
> open TCP
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
Hi,
The e-mail you have sent to this domain (qlusters.com) did not reach its
indended destination.
Possible reasons: the e-mail address entered is mispelled or the user is
none existant.
am I the only one getting this annoying message for each message sent to
the list? Looks to me like either t
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
On Mon, Nov 17, 2003 at 04:02:58PM +, [EMAIL PROTECTED] wrote:
> Hi,
>
> I have an idea that would be nice to try and could
> also be a useful test of our administration tools.
>
> We create a virtual server and auto migrate it
> from one hosting server to another, to another
good idea,
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
Hi,
I have an idea that would be nice to try and could
also be a useful test of our administration tools.
We create a virtual server and auto migrate it
from one hosting server to another, to another
--
Lending not allowed
Reading aloud not allowed
_
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
On Mon, Nov 17, 2003 at 08:53:56AM -0400, James MacLean wrote:
> Hi Matt,
>
> On my system, when it Oopses, it's down for the count. No ping or
> anything. Keyboard lights flashing just to point out it's in bad shape :).
when the keyboard leds start to flash, it's a panic
and you should capture/
On Mon, Nov 17, 2003 at 06:23:00AM -0500, Matt Ayres wrote:
> I have 2 servers who keep crashing, sometimes every few hours... I am
> still working on a console solution so I don't know the exact place
> where the problem is.
Hi Matt!
> The servers are in a "half hung" state, they respond to PING
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
Hi all!
Here the list from Paul, with my comments
where appropriate ;)
]Needs fixing: as of 2003 Jan 26 Paul Sladen <[EMAIL PROTECTED]>
okay, maybe an update should be done, paul?
](This is kernel side stuff considered, not userspace)
I'll comment on that one by one ...
]-
The e-mail you have sent to this domain (qlusters.com) did not reach its indended
destination.
Possible reasons: the e-mail address entered is mispelled or the user is none existant.
Note:
-
You may see the original e-mail below. If you feel that this is error message is
incorrect or
yo
Hi Matt,
On my system, when it Oopses, it's down for the count. No ping or
anything. Keyboard lights flashing just to point out it's in bad shape :).
I saw the oops this morning, but didn't copy all the register data and
stack log as it is always so much to pencil down :), and I was hoping this
I have 2 servers who keep crashing, sometimes every few hours... I am
still working on a console solution so I don't know the exact place
where the problem is.
The servers are in a "half hung" state, they respond to PING and will
open TCP connections, but they won't send any data back.
Is this ho
Hi folks,
2 nights in a row at 4:00am when netstat runs, the system is Oopsing. I
was running vs1.1.2 and am now upgrading to vs1.1.3 but do not see
anything that suggests a fix in in the diffs.
Possibly I am the only lucky one :)? I remember this happening some time
ago in earlier vservers, a
On Sun, 16 Nov 2003, ian douglas wrote:
> how about "from the very beginning" documentation? ie: explain things for
> people that need more stepped instructions than "patch the kernel" (ie:
> explain how to apply a .diff file etc.), which OS's vserver has been tested
> on, etc.
We should point th
I dont believe in santa! >:o[
hihihi
-Mensagem original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] nome de Herbert Poetzl
Enviada: segunda-feira, 17 de Novembro de 2003 2:36
Para: [EMAIL PROTECTED]
Assunto: [Vserver] XMas Wishlist
Hi All!
feel free to add your wishes ...
http:/
40 matches
Mail list logo
