[CRIU] Dumping Process - lxc-ls -f Problem

[Thouraya TH]

Hi all,

Please, is this message "782: Error (sk-inet.c:610): Can't bind inet
socket: Invalid argument"  means that there is a port occupied ?


Thank you so much for help.
Best regards.



2015-06-20 12:45 GMT+01:00 Thouraya TH <thouraya87 at gmail.com>:

> Hi,
>
> *Can you show us the decoded sk-inet image?*
>
> How can i do that please ?
> Thank you so much.
> Best Regards.
>
>
>
> 2015-06-19 14:11 GMT+01:00 Pavel Emelyanov <xemul at parallels.com>:
>
>> On 06/18/2015 06:24 PM, Thouraya TH wrote:
>> > Hello all;
>> >
>> > Here is a link to the restore.log file (i have used the -v option)
>> > https://www.dropbox.com/s/vfiy6lqkibvco8m/restore.log?dl=0
>>
>> 159MB of logs :) Impressive!
>>
>> > without -v option, i have only these lines:
>> >
>> > Warn  (cr-restore.c:1029): Set CLONE_PARENT | CLONE_NEWPID but it might
>> cause restore problem,because not all kernels support such clone flags
>> combinations!
>> > RTNETLINK answers: File exists
>> > RTNETLINK answers: File exists
>> > RTNETLINK answers: File exists
>> >    782: Error (sk-inet.c:610): Can't bind inet socket: Invalid argument
>>
>> So, it looks like the socket in question is
>>
>> (11.553205)   1047:     Restore: family 10 type 2 proto 17 port 123 state
>> 7 src_addr fe80::216:3eff:fefd:32e6
>> (11.553236)   1047: Error (sk-inet.c:610): Can't bind inet socket:
>> Invalid argument
>>
>> It's IPv6 and bind() reports EINVAL. This can be for several reasons and
>> I think
>> that the "real" one is -- the address is link-local but socket is not
>> bound to
>> device yet.
>>
>> Can you show us the decoded sk-inet image?
>>
>> -- Pavel
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20150621/a8476235/attachment.html>