Re: Starting Openvz
On Monday 28 August 2006 15:35, John Kelly wrote:
> On Mon, 28 Aug 2006 09:22:33 +0300, David Baron <d_baron@012.net.il>
>
> wrote:
> >Startup of Openvz, which I assume "populates" /dev/vzdev
>
> I don't have a /dev/vzdev
>
> >fails with an error message "unregistered protocal family 17"
> >
> >Doing a grep on dmesg for such yields:
> >NET: Registered protocol family 17
> >NET: Unregistered protocol family 17
> >NET: Registered protocol family 17
> >
> >Yes? No? Any ideas?
>
> These are normal messages.
>
> >Should I move the startup for openvz to the very end
>
> Mine looks like:
>
> S10sysklogd
> S11klogd
> S14ppp
> S15bind9
> S18portmap
> S20inetd
> S20makedev
> S20rsync
> S20ssh
> S20vsftpd
> S20vz
> S25mdadm
> S25nfs-user-server
> S83chrony
> S89cron
> S99rmnologin
> S99stop-bootlogd
>
> Works fine.
>
> You might try running /etc/init.d/vz manually, with "set -x" at the
> beginning, to get more information.
Running manually shows nothing about this protocal 17 stuff so this is
apparently from elsewhere, normal as you said, not relevant here.
Running /etc/init.d/vz start manually simply indicates "failed".
Running /etc/init.d/vz status shows "stopped"
( do not know what you mean by set -x here. )
The script is trying to modprobe a bunch of modules. I have no such modules:
vzdev, vzmon, vzdquota. However, the __echo error messages corresponding to
the various failures do not show.
Reply to: