-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: coroot-node-agent crashes the service rtpengine-daemon with "segmentation fault" #158
Comments
I can't reproduce this issue on Debian 12 with kernel version 6.11.5+bpo-amd64 |
Hi @def , this is weird. Steps to reproduceHere are the exact steps which I did on a fresh Debian 12 Install:
sudo apt update && sudo apt full-upgrade -y
sudo apt install -t bookworm-backports linux-image-amd64 linux-headers-amd64 -y
systemctl reboot
wget https://dfx.at/rtpengine/latest/pool/main/r/rtpengine-dfx-repo-keyring/rtpengine-dfx-repo-keyring_1.0_all.deb
sudo dpkg -i rtpengine-dfx-repo-keyring_1.0_all.deb
echo "deb [signed-by=/usr/share/keyrings/dfx.at-rtpengine-archive-keyring.gpg] https://dfx.at/rtpengine/latest bookworm main" | sudo tee /etc/apt/sources.list.d/dfx.at-rtpengine.list
sudo apt update && sudo apt install libavcodec-extra rtpengine -y
curl -sfL https://raw.githubusercontent.com/coroot/coroot-node-agent/main/install.sh | \
COLLECTOR_ENDPOINT=http://localhost:8080 \
SCRAPE_INTERVAL=15s \
sh -
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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: