Indeed, they weren't being run, but running them by hand doesn't seem to
Am I missing something?
# /etc/init.d/util-vserver status
> Path to vshelper has been set
> # /etc/init.d/vprocunhide status
> /proc entries were fixed
> # vserver -v vsrvdev1 start
> New network context is 2000
> Adding 22.214.171.124
> New security context is 2000
> No command given; use '--help' for more information.
> An error occured while executing the vserver startup sequence; when
> there are no other messages, it is very likely that the init-script
> () failed.
> Common causes are:
> * /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' build
> method knows how to deal with this, but on existing installations,
> appending 'true' to this file will help.
> Failed to start vserver 'vsrvdev1'
On Thu, Feb 8, 2018 at 4:27 PM, Ben Green <email@example.com> wrote:
> Quoting Daniel Urist <firstname.lastname@example.org>:
> I don't seem to be able to start vservers. I get the following error with a
>> newly built stretch vserver:
> This looks like a case of the init scripts not being run at boot. If you
> run them manually you can confirm that.
Received on Mon Feb 12 17:31:41 2018