You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have currently the problem, that coroot-node-agent crashes the service rtpengine-daemon with "segmentation fault"rtpengine-daemon.service: Main process exited, code=killed, status=11/SEGV.
Originally I have opened this issue at the sipwise/rtpengine issue: 1888 project (if additional context is needed).
Hi coroot-node-agent team,
I have currently the problem, that
coroot-node-agent
crashes the servicertpengine-daemon
with "segmentation fault"rtpengine-daemon.service: Main process exited, code=killed, status=11/SEGV
.Originally I have opened this issue at the sipwise/rtpengine issue: 1888 project (if additional context is needed).
Operating System
The OS is running as a VM on Proxmox 8.3.
I am using Debian 12 Bookworm Cloud Image.
Application Versions
Steps to reproduce the problem
rtpengine-daemon
.coroot-node-agent
.modprobe -v nf_conntrack
Workaround
coroot-node-agent
.modprobe -v nf_conntrack
systemctl start rtpengine-daemon
Logs Starting coroot-node-agent + rtpengine-daemon
Starting
coroot-node-agent
andrtpengine-daemon
withsystemctl start rtpengine-daemon coroot-node-agent && journalctl -u rtpengine-daemon -u coroot-node-agent -f
.Logs Starting just rtpengine-daemon
Starting
rtpengine-daemon
withsystemctl start rtpengine-daemon && journalctl -u rtpengine-daemon -f
.The text was updated successfully, but these errors were encountered: