<div dir="ltr">Hello all and thank you for your answer.<div><br></div><div>my "unshare" version doesn't support the same options as you</div><div><br></div><div><div>unshare --help</div><div><br></div><div>Usage:</div>
<div> unshare [options] <program> [args...]</div><div><br></div><div>Options:</div><div> -h, --help usage information (this)</div><div> -m, --mount unshare mounts namespace</div><div> -u, --uts unshare UTS namespace (hostname etc)</div>
<div> -i, --ipc unshare System V IPC namespace</div><div> -n, --net unshare network namespace</div></div><div><br></div><div>Anyway i'll wait for a next criu version which will hopefully support namespaces :)</div>
<div><br></div><div>Regards,</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014/1/22 Andrew Vagin <span dir="ltr"><<a href="mailto:avagin@parallels.com" target="_blank">avagin@parallels.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Tue, Jan 21, 2014 at 02:40:16PM +0100, Smain Kahlouch wrote:<br>
> Hello guys,<br>
><br>
> I don't know if it's the right place to post this issue but I didn't find<br>
> another way to contact you.<br>
><br>
> I'm currently testing lxc features ("docker" to be precise) and I'm facing the<br>
> following message when I try to use criu :<br>
><br>
><br>
> 1 - check if CRIU is working with my kernel :<br>
><br>
> criu check --ms<br>
> (00.012246) Warn (tun.c:55): Skipping tun support check<br>
> Looks good.<br>
><br>
> 2 - Identify what i want to dump, for example varnish:<br>
><br>
> init,1<br>
> ├─acpid,3886<br>
> ├─atd,3648<br>
> ├─auditd,3591<br>
> │ ├─audispd,3593<br>
> │ │ └─{audispd},3598<br>
> │ └─{auditd},3592<br>
> ├─cron,3781<br>
> ├─dbus-daemon,3883 --system<br>
> ├─docker,3732 -d -p /var/run/docker.pid -r=false -s devicemapper<br>
> │ ├─lxc-start,4592 -n<br>
> 9f81f7bc33c83fc1369b9355c959b6f0d8c87c6758bb75af3ae726ba2bad053a -f...<br>
> │ │ └─sh,4601 -c /bin/bash -c '/usr/local/sbin/runservices.sh; /usr/sbin/<br>
> sshd -D'<br>
> │ │ ├─bash,4685 -c /usr/local/sbin/runservices.sh; /usr/sbin/sshd -D<br>
> │ │ │ └─sshd,5022 -D<br>
> │ │ ├─cc-node,4774 /usr/bin/cc-node -d -p /var/run/cc-node.pid<br>
> │ │ │ └─{cc-node},4776<br>
> │ │ ├─collectdmon,4820 -P /var/run/collectdmon.pid -- -C /etc/<br>
> collectd/collectd.conf<br>
> │ │ │ └─collectd,4822 -C /etc/collectd/collectd.conf -f<br>
> │ │ │ ├─{collectd},4823<br>
> │ │ │ ├─{collectd},4824<br>
> │ │ │ ├─{collectd},4825<br>
> │ │ │ ├─{collectd},4826<br>
> │ │ │ ├─{collectd},4827<br>
> │ │ │ └─{collectd},4828<br>
> │ │ ├─rsyslogd,4729 -c5<br>
> │ │ │ ├─{rsyslogd},4737<br>
> │ │ │ ├─{rsyslogd},4738<br>
> │ │ │ └─{rsyslogd},4739<br>
> │ │ ├─ruby,4837 /usr/bin/collectd-interface-daemon -p 5000 -l /var/<br>
> log -P /var/run -I ...<br>
> │ │ │ └─{ruby},7084<br>
> │ │ └─varnishd,4792 -P /var/run/varnishd.pid -a :8000 -T :6082 -f /<br>
> etc/varnish/default.vcl -p ...<br>
> │ │ └─varnishd,4794 -P /var/run/varnishd.pid -a :8000 -T :6082 -f<br>
> /etc/varnish/default.vcl -p ...<br>
> │ │ ├─{varnishd},4795<br>
> │ │ ├─{varnishd},4796<br>
> │ │ ├─{varnishd},4797<br>
> │ │ ├─{varnishd},4798<br>
> │ │ ├─{varnishd},4800<br>
> │ │ ├─{varnishd},4801<br>
> │ │ ├─{varnishd},4802<br>
> │ │ ├─{varnishd},4803<br>
> │ │ ├─{varnishd},4804<br>
> │ │ ├─{varnishd},4805<br>
> │ │ ├─{varnishd},4806<br>
> │ │ ├─{varnishd},4807<br>
> │ │ ├─{varnishd},4808<br>
> │ │ ├─{varnishd},4809<br>
> │ │ ├─{varnishd},4810<br>
> │ │ ├─{varnishd},4811<br>
> │ │ ├─{varnishd},4812<br>
> │ │ └─{varnishd},4813<br>
><br>
> 3 - try to dump<br>
><br>
> criu dump --tree 4792 --images-dir /data/ --leave-stopped<br>
> pie: Error (pie/parasite.c:243): mount failed (-1)<br>
> pie: Error (pie/parasite.c:474): Close the control socket for writing<br>
> ><br>
> (00.095409) Error (parasite-syscall.c:787): Can't retrieve FD from socket<br>
> (00.095454) Error (parasite-syscall.c:297): Message reply from daemon is<br>
> trimmed (12/0)<br>
> (00.095468) Error (cr-dump.c:1441): Can't get proc fd (pid: 4792)<br>
> (00.096172) Error (cr-dump.c:1811): Dumping FAILED.<br>
><br>
><br>
> I built a custom kernel from 3.12.6 debian sources.<br>
><br>
> I followed the instructions in your website<br>
><br>
> Could you please help me to fix that.<br>
<br>
</div></div>You are trying to dump a task from another pidns. Unfortunately it's<br>
unsupported by now. I'm going to fix that. I think it will not require too<br>
much time. Thank you for the report.<br>
<br>
Currently you can workaround this issue, if you enter in this pidns and<br>
mount procfs in /proc.<br>
<br>
unshare -m nsenter -p -t PID criu.sh<br>
<br>
# cat criu.sh<br>
set -e<br>
mount -make-rprivate /<br>
mount -t proc proc /proc<br>
criu dump --tree PID --images-dir /data/ --leave-stopped<br>
<br>
><br>
> Thanks,<br>
> Smana<br>
<br>
> _______________________________________________<br>
> CRIU mailing list<br>
> <a href="mailto:CRIU@openvz.org">CRIU@openvz.org</a><br>
> <a href="https://lists.openvz.org/mailman/listinfo/criu" target="_blank">https://lists.openvz.org/mailman/listinfo/criu</a><br>
<br>
</blockquote></div><br></div>