[CRIU] Updating conf or changes in files generate "Error: Restoring failed"

Roberto Del Aguila Rivera delaguila at clasxxi.edu.mx
Tue Nov 25 23:45:06 PST 2014


Thanks Pavel. The change in the file was made by hand and it was even an
error. What we have clear now is that every file involved with Apache
should not be changed to avoid this errors. The only question is, what
happens if we continue using Apache from the first restore and it's Apache
who made the changes to the logs or to the confs? We haven't tried that but
we are wondereing if it will happens the same error.

Thaks in advance.
Roberto.



2014-11-25 13:06 GMT-06:00 Pavel Emelyanov <xemul at parallels.com>:

> On 11/25/2014 11:47 AM, Roberto Del Aguila Rivera wrote:
> > Thanks a lot Pavel. (I don't know if it's ok to copy this large file
> here).
> >
> > ...
> > (00.039488)   2001: Error (files-reg.c:820): File
> var/log/apache2/error.log has bad size 109 (expect 100)
> > (00.039560) Error (cr-restore.c:1780): Restoring FAILED.
>
> OK, here it is. The file size has changed. We have this check to try
> to make sure filesystem is in the same state as it used to be on dump,
> so that applications can continue working.
>
> Can you describe what you're trying to do with apache, why has
> the error.log's size has changed in such a strange way (plus
> 9 bytes)?
>
> Thanks,
> Pavel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20141126/9f410a3e/attachment.html>


More information about the CRIU mailing list