lglhust
commented
4 months ago sorry, i made a mistake. The log-level is wrong.
Closed lglhust closed 4 months ago
lglhust
commented
4 months ago sorry, i made a mistake. The log-level is wrong.
rtpengine version the issue has been seen with
Version: 10.4.1.7+0~mr10.4.1.7 git-mr10.4.1-0b6d0a0d
Used distribution and its version
Ubuntu 22.04.4 LTS
Linux kernel version used
5.15.0-107-generic
CPU architecture issue was seen on (see
uname -m)x86_64
Expected behaviour you didn't see
I tried to modified rtpengine.conf in two ways as: 1 first trying: log_file = /var/log/rtpengine.log log-level = 0
in /lib/systemd/system/rtpengine-daemon.service: "ExecStart=/usr/sbin/rtpengine -f --pidfile /run/rtpengine/ngcp-rtpengine-daemon.pid --config-file /etc/rtpengine/rtpengine.conf "
and I restarted rsyslog and rtpengine, but found no rtpengine log.
2 second trying: I also tried to use rsyslog as:
log_file = /var/log/rtpengine.log
log-level = 0
log-stderr = false
log-facility = local3
log-facility-cdr = local0
log-facility-rtcp = local3
and modified /etc/rsyslog.conf as: local3.* -/var/log/rtpengine.log
and I restarted rsyslog and rtpengine, but found no rtpengine log.
Did i miss something in /etc/rtpengine/rtpengine.conf? Thanks.
Unexpected behaviour you saw
I found no log file output in /var/log while the rtpengine.service and ngcp-rtpengine-daemon.service are active (running).
Steps to reproduce the problem
I tried to modified rtpengine.conf as:
log_file = /var/log/rtpengine.log log-level = 0
in /lib/systemd/system/rtpengine-daemon.service ExecStart=/usr/sbin/rtpengine -f --pidfile /run/rtpengine/ngcp-rtpengine-daemon.pid --config-file /etc/rtpengine/rtpengine.conf
and I restarted rsyslog and rtpengine, but found no rtpengine log.
I also tried to use rsyslog as:
log_file = /var/log/rtpengine.log
log-level = 0
log-stderr = false
log-facility = local3
log-facility-cdr = local0
log-facility-rtcp = local3
and modified /etc/rsyslog.conf as: local3.* -/var/log/rtpengine.log
and I restarted rsyslog and rtpengine, but found no rtpengine log.
Additional program output to the terminal or logs illustrating the issue
No response
Anything else?
No response