[CRIU] Dumping a restored apache process

[Pavel Emelyanov]

On 04/16/2014 09:24 PM, Cyrill Gorcunov wrote:
> On Wed, Apr 16, 2014 at 07:48:07PM +0300, Deyan Doychev wrote:
>> On 04/16/2014 07:01 PM, Cyrill Gorcunov wrote:
>>> On Wed, Apr 16, 2014 at 06:18:01PM +0300, Deyan Doychev wrote:
>>>> 3. criu restore --tcp-established --file-locks --restore-detached
>>>>     It successfully restores.
>>>>
>>>> 4. criu dump --tcp-established --file-locks -t 9499 -v4
>>>>     Here I get the error described above.
>>> Could you please provide complete dump log for step 4)
>>
>> Here is the complete dump log.
>>
>> This time I hit the error on the third dump.
>>
> 
> Thanks! Indeed for some reason the file descriptor is treated as
> different one keeping the same socket

Since it's the after-restore problem, maybe we _restore_ these files
as two different ones?

> (00.060776) 19463 fdinfo 4: pos: 0x               0 flags:                2/0x1
> (00.060782) 	Searching for socket 126d548 (family 10)
> (00.060789) No filter for socket
> (00.060796) Dumping inet socket at 4
> (00.060798) 	Dumping: ino 0x 126d548 family   10 type    1 port       80 state 10 src_addr ::
> (00.060802) 	Dumped: family 10 type 1 proto 6 port 80 state 10 src_addr ::
> ...
> (00.076683) 19465 fdinfo 4: pos: 0x               0 flags:                2/0x1
> (00.076689) 	Searching for socket 126d548 (family 10)
> (00.076692) Error (sk-inet.c:250): BUG at sk-inet.c:250
> 
> Investigating...
> _______________________________________________
> CRIU mailing list
> CRIU at openvz.org
> https://lists.openvz.org/mailman/listinfo/criu
> .
>