Reactive mode failed to switch on

I’ve installed DataLore on Vmware workstation 16 pro with centos 8.4.
Here is my OS hardware info:

When I run DataLore, log in, open notebook and open “Reactive mode”, the tip on the bottom-right of the window shows me “Kernel failed”.

Why is that happened? Is it the reason of DataLore not supporting Vmware?

Hello @meatjam,
which kernel version are you using? Reactive mode might not work with host kernel version < 5.13

Thx for your reply. I’ve tried upgrading my centos kernel version to 6.1.1, but the problem remains.
image

Thank you, could you please share some logs from the agent container?

I’ve used command “docker logs” to check the datalore agent containers’s logs, and get these things:

12:33:18.186 INFO [EvaluatorListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77] j.d.n.s.u.s.SocketListeningThread - Thread[EvaluatorListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77,5,main]: EOF received
12:33:18.237 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - Killing evaluator
12:33:18.237 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - evaluator killed in 0
12:33:18.237 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - Killing terminal
12:33:18.238 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - terminal killed in 1
12:33:18.246 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.a.WebdavDirectoryAttachController - Webdav was successfully mounted
12:33:18.676 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Terminal process is not alive, restarting…
12:33:18.676 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - Killing terminal
12:33:18.676 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - terminal killed in 0
12:33:18.676 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Terminal process starting
12:33:18.676 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Command: sh /opt/datalore/terminal_entrypoint.sh
12:33:19.025 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Terminal process started: Process[pid=181303, exitValue=“not exited”]
12:33:19.026 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Terminal process has been restarted
12:33:19.031 INFO [TerminalListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77] j.d.n.s.u.s.SocketListeningThread - Thread[TerminalListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77,5,main]: EOF received
12:33:24.459 INFO [EvaluatorListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77] j.d.n.s.u.s.SocketListeningThread - Thread[EvaluatorListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77,5,main]: EOF received
12:33:24.512 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - Killing evaluator
12:33:24.513 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - evaluator killed in 1
12:33:24.513 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - Killing terminal
12:33:24.513 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - terminal killed in 0
12:33:24.520 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.a.WebdavDirectoryAttachController - Webdav was successfully mounted
12:33:24.930 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Terminal process is not alive, restarting…
12:33:24.930 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - Killing terminal
12:33:24.930 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.u.s.ProcessConnector - terminal killed in 0
12:33:24.930 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Terminal process starting
12:33:24.931 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Command: sh /opt/datalore/terminal_entrypoint.sh
12:33:25.268 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Terminal process started: Process[pid=181334, exitValue=“not exited”]
12:33:25.269 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.p.PythonTerminalProcess - Terminal process has been restarted
12:33:25.279 INFO [TerminalListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77] j.d.n.s.u.s.SocketListeningThread - Thread[TerminalListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77,5,main]: EOF received
12:33:26.389 INFO [EvaluatorListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77] j.d.n.s.u.s.SocketListeningThread - Thread[EvaluatorListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77,5,main]: EOF received
12:33:26.390 ERROR [EvaluatorListener-HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77] j.d.n.s.a.p.PythonEvaluationProcess - Evaluator connection lost
12:33:41.407 INFO [ComputationAgent_0f10811dc6f6] j.d.n.s.a.a.WebdavDirectoryAttachController - Webdav was successfully mounted
12:33:42.011 INFO [pool-2-thread-1] j.d.n.s.analysisServer.SdkUpdater - Updating skeletons…
12:33:42.664 INFO [pool-2-thread-1] j.d.n.s.analysisServer.SdkUpdater - Updated skeletons
file:///data/notebook_files refresh took 1 ms
0 file(s) added, 0 file(s) updated, 0 file(s) deleted

file:///opt/datalore/python refresh took 1 ms
0 file(s) added, 0 file(s) updated, 0 file(s) deleted

file:///var/datalore/manager/.pip refresh took 0 ms
0 file(s) added, 0 file(s) updated, 0 file(s) deleted

I should have shown you these logs at first, but I’m new to use docker, sorry for that.
Here is another part of logs:

2023-02-14 12:33:43,230|kernel_runner|ERROR |HqLr1OMPpVtGcMUqmXSxd9/pIF2L4t2DG3XPk1ZS5ln77|The kernel crashed with an exception
Traceback (most recent call last):
File “/opt/datalore/python/kernel_runner/kernel_runner.py”, line 49, in run
await computation_module.Computation(kernel_manager, evaluator_factory, read_request, write_reply).run()
File “/opt/datalore/python/kernel_runner/computation/reactive/reactive_computation.py”, line 56, in run
await self._process_init()
File “/opt/datalore/python/kernel_runner/computation/reactive/reactive_computation.py”, line 82, in _process_init
await self._kernel_client.checkpoint()
File “/opt/datalore/python/kernel_runner/computation/reactive/persistent_client.py”, line 17, in checkpoint
await self._client.parent.kernel.checkpoint()
File “/opt/datalore/python/kernel_runner/computation/reactive/persistent_process.py”, line 36, in checkpoint
await self._exec(decorate_with_sudo(command))
File “/opt/datalore/python/kernel_runner/computation/reactive/persistent_process.py”, line 116, in _exec
raise RuntimeError(f’Error executing command “{command}”, status={proc.returncode}\n{stderr.decode()}')
RuntimeError: Error executing command “sudo /usr/sbin/criu dump -v1 --leave-running --track-mem --shell-job --tree 201375 --images-dir /tmp/datalore-3x5v4qbn/0”, status=1
Error (criu/util.c:641): exited, status=1
Error (criu/util.c:641): exited, status=1
Error: Compatible vdso’s size is bigger than reserved buf
Error (criu/vdso.c:441): vdso: Compat vdso helper exited with 255
Error (criu/vdso.c:498): vdso: Failed to mmap compatible vdso with helper process
Error (criu/vdso.c:620): vdso: Failed to fill compat vdso symtable
Error (criu/kerndat.c:1594): kerndat_vdso_fill_symtable failed when initializing kerndat.
Error (criu/crtools.c:260): Could not initialize kernel features detection.

  • PHASE=up
  • MOUNT_LOG=/tmp/host/wb-pIF2L4t2DG3XPk1ZS5ln77.log
  • ‘[’ up = up ‘]’
    ++ mount
    ++ grep /data/notebook_files
    ++ wc -l
  • IS_MOUNTED=1
  • (( 1 > 0 ))
  • exit 1