OpenVZ Forum: Support » Fedora 16 containers problem

Home » General » Support » Fedora 16 containers problem

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Fedora 16 containers problem [message #44950]

Mon, 16 January 2012 19:10

mperkel
Messages: 253
Registered: December 2006

Senior Member

Upgraded for Fedora 14 to Fedora 16 in a container using you.

After the upgrade I ran yum install upstart and then restarted the container. The container runs but no services start.

When I try to start something I get this:

service crond restart
Failed to get D-Bus connection: No connection to service manager.

What am I missing?

Thanks in advance

Junk Email Filter
http://www.junkemailfilter.com

Report message to a moderator

Re: Fedora 16 containers problem [message #45840 is a reply to message #44950]

Fri, 06 April 2012 14:25

acv0ru
Messages: 2
Registered: May 2011
Location: RU

Junior Member

i have the some problem

any service show

Redirecting to /bin/systemctl  stop sshd.service
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: No such file or directory

Report message to a moderator

Re: Fedora 16 containers problem [message #46194 is a reply to message #44950]

Tue, 01 May 2012 18:37

potatosalad
Messages: 3
Registered: May 2012

Junior Member

Fedora 16 with systemd requires the newer vzctl 3.2, older versions have some workarounds that get the container to use upstart. You can grab the latest vzctl from download.openvz.org/utils/nightlies/vzctl/current/

See the vzctl 3.2 changes: wiki.openvz.org/Download/vzctl/3.2/changes

Report message to a moderator

Previous Topic:	VPs wont boot and kernel error while updating
Next Topic:	How to enter a "Not Running Container"

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Sep 27 07:31:39 GMT 2024

Total time taken to generate the page: 0.04314 seconds