Going back through your logs with the version information you've
provided, I'm pretty sure that the problem is your old kernel version
not supporting the necessary features for mountall
** Package changed: upstart (Ubuntu) => mountall (Ubuntu)
** Changed in: mountall (Ubuntu)
Status: Incom
That kernel version (2.6.24) is awfully old.
I'm not sure that any of this will actually work with it!
--
Upstart fails to boot in an OpenVZ VPS
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
FYI I filed a bug upstream (with OpenVZ) linking back to this bug report
as well.
http://bugzilla.openvz.org/show_bug.cgi?id=533
I attached it to the older report from 2007.
** Bug watch added: OpenVZ Bugzilla #533
http://bugzilla.openvz.org/show_bug.cgi?id=533
--
Upstart fails to boot in a
Here is a link to some of the discussion from 2007 , the last time that
I know this was an issue :
http://www.mail-archive.com/upstart-de...@lists.ubuntu.com/msg00120.html
Unfortunately I do not see a fix in that discussion, but perhaps it will
give a lead ?
--
Upstart fails to boot in an OpenV
How it *should* work:
The VSP is started with vzctl start xxx
vzctrl should then set up all network interfaces inside the Container,
initialize the Container quota, if needed, start the init process inside
the Container.
--
Upstart fails to boot in an OpenVZ VPS
https://bugs.launchpad.net/bugs/
I do not know how openvz "boots" the VPS.
Similare to a chroot, the guest uses the host kernel which is patched
with the oopenvz kernel patch.
>From my 9.10 (broken) VPS:
r...@test:/# init --version
init (upstart 0.6.3)
Copyright (C) 2009 Canonical Ltd.
This is free software; see the source for
Also what does "uname -a" say when run inside the container?
--
Upstart fails to boot in an OpenVZ VPS
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
So far, I don't see any evidence that Upstart is actually running in
your container - to me it looks like OpenVZ is using a different init
system entirely.
What does "init --version" say when run from inside the container?
What does "readlink /proc/1/exe" say?
--
Upstart fails to boot in an Ope
With the exception of init.log , the logs are all empty
r...@new:/var/log# cat init.log
starting init logger
init: hwclock main process (24) terminated with status 77
mountall:/proc/self/mountinfo: No such file or directory
init: mountall main process (25) killed by SEGV signal
This is what star
Example, make a new up to date ubuntu 9.10 template, boot it
Start the guest
Problem 1 - NO NETWORKING :(
r...@new:/# ping google.com
ping: unknown host google.com
PROBLEM 2 - UPSTART IS NOT WORKING
Lets start it with upstart
r...@new:/# service networking restart
restart: Unknown instance:
I can attach my template if you wish.
Honestly, no offense, but somebody familiar with VPS needs to look at
this along with someone familiar with Upstart or at least the boot
scripts.
If you do not know anything about VPS or OpenVZ, my bug report is not
going to make sense.
If you would like, do
Perhaps you could attach your template, that might shed some light on
things?
--
Upstart fails to boot in an OpenVZ VPS
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
I want you to pass --debug to the init daemon, pid 1, the process that
is started by the kernel.
--
Upstart fails to boot in an OpenVZ VPS
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-
Are you familiar with OpenVZ ? VPS ?
http://wiki.openvz.org/Main_Page
You build a "template" which then runs as a guest on the host node.
There are several guides for how to do this, basically you use
debootstrap
http://wiki.openvz.org/Debian_template_creation
You then start or boot the guest.
I'm sorry, but I just don't know what you're trying to show me.
Could you explain, in detail, what your issue is?
--
Upstart fails to boot in an OpenVZ VPS
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
There should be no /etc/init.d/networking script - your system may be
out of date
--
Upstart fails to boot in an OpenVZ VPS
https://bugs.launchpad.net/bugs/436130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
Fresh template (just made from scratch)
r...@new:/# ping google.com
ping: unknown host google.com
r...@new:/# service netwroking restart
netwroking: unrecognized service
r...@new:/# init 2
r...@new:/# ping google.com
ping: unknown host google.com
r...@new:/# ifconfig
r...@new:/# /etc/init.d/networ
What are your wanting ?
r...@banshee~# vzctl start 106
Warning: Unknown iptable module: ipt_recent, skipped
Starting container ...
Container is mounted
Adding IP address(es): 10.10.10.2
Setting CPU units: 1000
Configure meminfo: 65536
Set hostname: test
File resolv.conf was modified
Container star
Try adding --debug to the kernel command line and capture the output
** Changed in: upstart (Ubuntu)
Status: New => Incomplete
** Changed in: upstart (Ubuntu)
Importance: Undecided => Low
--
Upstart fails to boot in an OpenVZ VPS
https://bugs.launchpad.net/bugs/436130
You received thi
19 matches
Mail list logo
