Displaying 4 results from an estimated 4 matches for "initpid".
Did you mean:
initid
2013 Feb 09
1
OSX rpcgen problem
...e[3]: Nothing to be done for `all'.
make[3]: Nothing to be done for `all-am'.
Making all in src
GEN util/virkeymaps.h
GEN locking/lock_protocol.h
GEN locking/lock_protocol.c
GEN locking/lock_daemon_dispatch_stubs.h
GEN lxc/lxc_protocol.h
unsigned hyper initpid;
^^^^^^^^^^^^^^^^^^^^^^^^^^
lxc/lxc_protocol.x, line 18: expected ';'
cannot shutdown /usr/bin/rpcgen: at ./rpc/genprotocol.pl line 124.
make[2]: *** [lxc/lxc_protocol.h] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2
I built using the following command line:
PATH=...
2015 Nov 20
2
signal for shutdown in lxc driver
...default init.
My problem is that I could not shutdown container correctly with libvirt.
virsh -c lxc:/// shutdown test
Domain test is being shutdown
In container I see only:
"init: Re-executing /sbin/init"
in syslog messages
Why it is happened?
lxcDomainShutdownFlags [1] send SIGTERM to initpid. Upstart got it and
reloaded himself instead shutdown. It's default behavior... [2]
The question is why libvirt send SIGTERM? As I can see lxc-stop [3]
send SIGPWR (that works correctly with upstart) and also have ability
to change default signals.
I can understand that when container start wi...
2015 Nov 20
0
Re: signal for shutdown in lxc driver
...d not shutdown container correctly with libvirt.
> virsh -c lxc:/// shutdown test
> Domain test is being shutdown
> In container I see only:
> "init: Re-executing /sbin/init"
> in syslog messages
>
> Why it is happened?
> lxcDomainShutdownFlags [1] send SIGTERM to initpid. Upstart got it and
> reloaded himself instead shutdown. It's default behavior... [2]
> The question is why libvirt send SIGTERM? As I can see lxc-stop [3]
> send SIGPWR (that works correctly with upstart) and also have ability
> to change default signals.
>
> I can understand...
2016 Mar 18
0
Fwd: [Issue]: Regarding client socket getting closed from the server once the lxc container is started
...Folks,
Using libvirt python bindings we are creating an lxc container.Here is the
problem that we see sometimes (say 20 % of the time) when we create a new
container.
1.container gets created, and also starts.However the we are not able to
enter the namepace of the container.It throws an error initPid not
available.We see that the using netstat command , socket connection is
closed.
2.To get around this problem we have to stop and start the container
again.We see that socket under (/var/run/libvirt/*) connection is
established and we are able to enter the namespace.
Enabled the libvirtd debu...