The Mathematica Jupyter kernel works fine, but generates the following crash. It is still quite difficult to understand when this crash is generated. I am using
Ubuntu 20.04
Mathematica 12.2.0
JupyterHub
Here are the first lines of the crash file available at : /var/crash/_opt_mathematica_SystemFiles_Kernel_Binaries_Linux-x86-64_WolframKernel.1001.crash
Hi,
The Mathematica Jupyter kernel works fine, but generates the following crash. It is still quite difficult to understand when this crash is generated. I am using
Here are the first lines of the crash file available at : /var/crash/_opt_mathematica_SystemFiles_Kernel_Binaries_Linux-x86-64_WolframKernel.1001.crash
<===== ProblemType: Crash Architecture: amd64 Date: Fri Apr 16 21:19:42 2021 DistroRelease: Ubuntu 20.04 ExecutablePath: /opt/mathematica/SystemFiles/Kernel/Binaries/Linux-x86-64/WolframKernel ExecutableTimestamp: 1618575522 ProcCmdline: /opt/mathematica/SystemFiles/Kernel/Binaries/Linux-x86-64/WolframKernel -script /home/jupyter-ffayard/WolframLanguageForJupyter/WolframLanguageForJupyter/Resources/KernelForWolframLanguageForJupyter.wl /home/jupyter-ffayard/.local/share/jupyter/runtime/kernel-3b83a8e5-f01c-4544-9d2f-c6e1fa52a9f9.json ScriptInstall ProcCwd: /home/jupyter-ffayard ProcEnviron: LC_TIME=fr_FR.UTF-8 LC_MONETARY=fr_FR.UTF-8 PATH=(custom, no user) LC_ADDRESS=fr_FR.UTF-8 LANG=en_US.UTF-8 LC_TELEPHONE=fr_FR.UTF-8 SHELL=/bin/bash LC_NAME=fr_FR.UTF-8 LC_MEASUREMENT=fr_FR.UTF-8 LC_IDENTIFICATION=fr_FR.UTF-8 LC_NUMERIC=fr_FR.UTF-8 LC_PAPER=fr_FR.UTF-8 ... =====>
I have tried to launch the command responsible for the crash from the shell, and I get the following output
<=====
SocketOpen::zmqexception: A ZeroMQ exception was thrown - Address already in use (code 98)
SocketOpen::zmqexception: A ZeroMQ exception was thrown - Address already in use (code 98)
SocketOpen::zmqexception: A ZeroMQ exception was thrown - Address already in use (code 98)
General::stop: Further output of SocketOpen::zmqexception will be suppressed during this calculation. =====>
Is it a known problem ? Any workaround ?
Best regards and thanks for your help, Francois