OpenVZ Forum



Members   Search      Help    Register    Login    Home
Home » General » Support » Fedora 16 containers problem
Fedora 16 containers problem [message #44950] Mon, 16 January 2012 14:10 Go to next message
mperkel is currently offline mperkel
Messages: 243
Registered: December 2006
Senior Member
From: *snfcca.dsl-w.verizon.net
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


Re: Fedora 16 containers problem [message #45840 is a reply to message #44950] Fri, 06 April 2012 10:25 Go to previous messageGo to next message
acv0ru is currently offline acv0ru
Messages: 2
Registered: May 2011
Location: RU
Junior Member
From: *moldtelecom.md
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


Re: Fedora 16 containers problem [message #46194 is a reply to message #44950] Tue, 01 May 2012 14:37 Go to previous message
potatosalad is currently offline potatosalad
Messages: 3
Registered: May 2012
Junior Member
From: *cpe.cableone.net
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
Previous Topic:VPs wont boot and kernel error while updating
Next Topic:How to enter a "Not Running Container"
Goto Forum:
  


Current Time: Sun May 26 05:08:17 EDT 2013
Powered by FUDforum Powered by Parallels Virtuozzo Containers