checkpoint-restore / criu

Checkpoint/Restore tool
criu.org
Other
2.86k stars 576 forks source link

Getting "Unexpected 104723 task interruption, aborting (01.038251) .Can't infect (pid: 104723) with parasite" error while doing criu dump #2227

Open gshhrm opened 1 year ago

gshhrm commented 1 year ago

Description I'm trying criu dump with a linux process(which is an Oracle WebLogic Server process) and I'm getting "Unexpected 104723 task interruption, aborting (01.038251) .Can't infect (pid: 104723) with parasite" error.

Steps to reproduce the issue: I'm using a shell script which performs certain operations such as flushing DB connections before calling the criu dump command. The criu command used is : criu dump -D ${REPO}/CRIU -v${LOGLEVEL} --shell-job --leave-running --log-file ${REPO}/CRIU/log -t $PID

Describe the results you received: I'm getting the error "Unexpected 104723 task interruption, aborting (01.038251) .Can't infect (pid: 104723) with parasite". I tried googling regarding this but wasn't able to find anything to help.

Describe the results you expected: I've tried executing the script for the same process on two linux machines and it's working for one machine but not for the other one. Here's a comparison of both the machines if that might be helpful image

Additional information you deem important (e.g. issue happens only occasionally):

CRIU logs and information:

criu_dump_log.txt

CRIU full dump/restore logs:

``` (paste your output here) ```

Output of `criu --version`:

``` Version: 3.12 ```

Output of `criu check --all`:

``` Error (criu/cr-check.c:625): Kernel doesn't support PTRACE_O_SUSPEND_SECCOMP Error (criu/cr-check.c:669): Dumping seccomp filters not supported: Input/output error Error (criu/cr-check.c:888): cgroupns not supported. This is not fatal. Warn (criu/cr-check.c:1060): Do not have API to map vDSO - will use mremap() to restore vDSO Warn (criu/cr-check.c:1026): compat_cr is not supported. Requires kernel >= v4.12 Looks good but some kernel features are missing which, depending on your process tree, may cause dump or restore failure. ```

Additional environment details:

adrianreber commented 1 year ago

You should try it with a newer OS and newer version of CRIU. What you are currently using is really really old.

gshhrm commented 1 year ago

Thanks for the response. I was interested to know the difference between the two scenarios as the dump is working on one but not the other even though the criu, os versions are the same

github-actions[bot] commented 1 year ago

A friendly reminder that this issue had no activity for 30 days.