[CRIU] Restore failed. Exit code: 43

[Cyrill Gorcunov]

On Tue, Jan 20, 2015 at 03:06:39PM +0300, Pavel Emelyanov wrote:
> On 01/19/2015 10:31 PM, Paschalis Mpeis wrote:
> > I am trying to capture, and replay a simple benchmark application.
> > The application accepts as a command line argument (CLA) an integer value to denote whether we are capturing or restoring.
> > 
> > On both capture and restore, I run the CRIU initialisation staff (provide folder for images, etc).
> > 
> > I first run the application with the capture integer value. I set the leave_running option to true, I do the capture, which seems successful, and then the application continues execution and finishes.
> > 
> > Then, I want to replay the application, from the point it was checkpointed. So I run again the application, and I pass as a CLA the restore integer value. For this case, the application simply initialises CRIU, and then tries to restore from the existing images.
> > 
> > I get the following error:
> > " `- FAIL (exit 43)"
> 
> But that's not CRIU message. Who prints that and what does the "exit 43" mean?
> 
> > You can find attached the dump.log and restore.log.
> 
> The restore.log ends with
> 
> (00.025773) Restore finished successfully. Resuming tasks.
> (00.025795) 5084 was trapped
> (00.025797) `- Expecting exit
> (00.025804) 5084 was trapped
> (00.025806) 5084 is going to execute the syscall f
> (00.025823) 5084 was stopped
> (00.025836) 5084 was trapped
> (00.025838) 5084 is going to execute the syscall b
> (00.025853) 5084 was stopped
> (00.025857) Writing stats
> 
> I.e. CRIU thinks that tasks are up and running.

Yes, it means everything is up and fine. Paschalis could you please
provide more details on your case

 - the testing program itself
 - step-by-step how you checkpointed and restored it