Hello,
I'm trying to reboot from inside a vserver.
===With sysv init style:
test:/# reboot
Broadcast message from root (pts/1) (Mon Oct 9 09:45:00 2006):
The system is going down for reboot NOW!
shutdown: timeout opening/writing control channel /dev/initctl
init: timeout opening/writing
I'm experimenting with vserver to host several (domain specific) servers
as guests on a single machine. For example, the first guest is a gentoo
system running httpd and the second guest is a debian system running bind.
Now I want the processes of each guest systems to be scheduled as if it
Mehdi Bennani wrote:
Hello,
I'm trying to reboot from inside a vserver.
===With sysv init style:
test:/# reboot
Broadcast message from root (pts/1) (Mon Oct 9 09:45:00 2006):
The system is going down for reboot NOW!
shutdown: timeout opening/writing control channel /dev/initctl
init:
reboot -f gives the same result on both init styles
Interesting, even with sysv? What is left in the guest at that point?
Actually, with sysv, reboot -f doesn't return any error but the
vserver doesn't reboot
(ssh session isn't interrupted and the uptime shown by vserver-stat on
the host
Mehdi Bennani wrote:
reboot -f gives the same result on both init styles
Interesting, even with sysv? What is left in the guest at that point?
Actually, with sysv, reboot -f doesn't return any error but the
vserver doesn't reboot
(ssh session isn't interrupted and the uptime shown by
Actually, with sysv, reboot -f doesn't return any error but the
vserver doesn't reboot
(ssh session isn't interrupted and the uptime shown by vserver-stat on
the host doesn't go back to zero).
Hmm. How did you install the utils? Did you install them by hand? If so,
did you remember to run
Mehdi Bennani wrote:
Actually, with sysv, reboot -f doesn't return any error but the
vserver doesn't reboot
(ssh session isn't interrupted and the uptime shown by vserver-stat on
the host doesn't go back to zero).
Hmm. How did you install the utils? Did you install them by hand? If so,
did
I am running debian etch vserver with postgres 8.1
installed. I have Enable options stats_start_collector
and stats_row_level. However when postgres starts i get
thefollowing in the log.
LOG: could not resolve localhost: Name or service not
known
LOG: disabling statistics collector for lack
Sorry! There was a file named disabled in
/etc/vservers/.defaults/apps/vshelper/
I deleted it and now it works well in both init styles.
Thank you for your help.
Best regards,
Mehdi Bennani
___
Vserver mailing list
Vserver@list.linux-vserver.org
Hi there,
on Monday, October 9, 2006 at 3:29:55 PM there was posted:
vhn LOG: could not resolve localhost: Name or service not
vhn known
put localhost 127.0.0.1 (or better: your guest main IP) into the
file /etc/hosts in your guest - this should solve your problem.
--
regards 'n greez,
On Mon, Oct 09, 2006 at 11:24:07AM +0200, Robert Fenk wrote:
I'm experimenting with vserver to host several (domain specific)
servers as guests on a single machine. For example, the first guest is
a gentoo system running httpd and the second guest is a debian system
running bind.
Now I
On Mon, 9 Oct 2006 16:01:49 +0200
Guenther Fuchs [EMAIL PROTECTED] wrote:
Hi there,
on Monday, October 9, 2006 at 3:29:55 PM there was
posted:
vhn LOG: could not resolve localhost: Name or
service not
vhn known
put localhost 127.0.0.1 (or better: your guest main
IP) into the
file
On Mon, 09 Oct 2006 10:10:38 -0500
[EMAIL PROTECTED] wrote:
On Mon, 9 Oct 2006 16:01:49 +0200
Guenther Fuchs [EMAIL PROTECTED] wrote:
Hi there,
on Monday, October 9, 2006 at 3:29:55 PM there was
posted:
vhn LOG: could not resolve localhost: Name or
service not
vhn known
put localhost
On Mon, Oct 09, 2006 at 10:10:38AM -0500, [EMAIL PROTECTED] wrote:
On Mon, 9 Oct 2006 16:01:49 +0200
Guenther Fuchs [EMAIL PROTECTED] wrote:
Hi there,
on Monday, October 9, 2006 at 3:29:55 PM there was
posted:
vhn LOG: could not resolve localhost: Name or
service not
vhn known
hi,
i tried to compile the same kernel with patch-2.6.18-vs2.1.1-rc37.diff
but gcc complains about debug_cmd.h. Also, debug_cmd.h doesn't need to
be called in switch.c. I just commented it out and i was able to compile
the kernel again.
My settings are
#
# Linux VServer
#
#
Hi,
I have a problem to use USB scanner using
libusb in vserver.
It seems impossible to access to /proc/bus/usb/*
in vserver.
I modified the /usr/lib/util-vserver/defaults/vprocunhide-files
to add /proc/bus, but there is only /proc/bus/input and /proc/bus/pci.
I added the line to fstap to mount
On Mon, Oct 09, 2006 at 08:43:48PM +0200, Jimmy Jazz wrote:
hi,
i tried to compile the same kernel with patch-2.6.18-vs2.1.1-rc37.diff
but gcc complains about debug_cmd.h.
should be fixed in rc38
Also, debug_cmd.h doesn't need to be called in switch.c.
depends on your .config options,
17 matches
Mail list logo