NethVoice Proxy logfile flooding

LayLow · September 16, 2024, 8:51am

Hi,

My messages log is fludding with an continious stream of logentries from kamailio:

2024-09-16T10:48:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m44(52) WARNING: <script>: [DEV] - [NATMANAGE] - FLT_NATS and FLB_NATB not set
2024-09-16T10:48:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m48(56) WARNING: <script>: [DEV] - 62798c28-a116-49b4-a59a-2f720ed9031b NOTIFY-52588 - in dialog and direction OUT, doing RELAY
2024-09-16T10:48:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m48(56) WARNING: <script>: [DEV] - 62798c28-a116-49b4-a59a-2f720ed9031b NOTIFY-52588 - in RELAY route
2024-09-16T10:48:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m48(56) WARNING: <script>: [DEV] - 62798c28-a116-49b4-a59a-2f720ed9031b NOTIFY-52588 - direction: out / out (<null>)
2024-09-16T10:48:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;31;49m48(56) ERROR: nathelper [nathelper.c:1511]: sdp_1918(): Unable to parse sdp body
2024-09-16T10:48:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m48(56) WARNING: <script>: [DEV] - [NATMANAGE] - FLT_NATS and FLB_NATB not set
2024-09-16T10:48:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m38(46) WARNING: <script>: [DEV] - 5508f12b-c62f-4cf2-bd4f-d2f343486114 OPTIONS-53764 - in dialog and direction OUT, doing RELAY
2024-09-16T10:48:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m38(46) WARNING: <script>: [DEV] - 5508f12b-c62f-4cf2-bd4f-d2f343486114 OPTIONS-53764 - in RELAY route
2024-09-16T10:48:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m38(46) WARNING: <script>: [DEV] - 5508f12b-c62f-4cf2-bd4f-

and in the cluster log:

2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;31;49m47(55) ERROR: nathelper [nathelper.c:1511]: sdp_1918(): Unable to parse sdp body
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m47(55) WARNING: <script>: [DEV] - [NATMANAGE] - FLT_NATS and FLB_NATB not set
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m37(45) WARNING: <script>: [DEV] - 1329ae2b-922d-4ae5-ade4-e1ed368c8bbc OPTIONS-17536 - in dialog and direction OUT, doing RELAY
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m37(45) WARNING: <script>: [DEV] - 1329ae2b-922d-4ae5-ade4-e1ed368c8bbc OPTIONS-17536 - in RELAY route
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m37(45) WARNING: <script>: [DEV] - 1329ae2b-922d-4ae5-ade4-e1ed368c8bbc OPTIONS-17536 - direction: out / out (<null>)
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m37(45) WARNING: <script>: [DEV] - [NATMANAGE] - FLT_NATS and FLB_NATB not set
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m36(44) WARNING: <script>: [DEV] - a00f1b12-f12f-44c7-9508-226ff77cf4e0 OPTIONS-31067 - in dialog and direction OUT, doing RELAY
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m36(44) WARNING: <script>: [DEV] - a00f1b12-f12f-44c7-9508-226ff77cf4e0 OPTIONS-31067 - in RELAY route
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m36(44) WARNING: <script>: [DEV] - a00f1b12-f12f-44c7-9508-226ff77cf4e0 OPTIONS-31067 - direction: out / out (<null>)
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m36(44) WARNING: <script>: [DEV] - [NATMANAGE] - FLT_NATS and FLB_NATB not set
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m37(45) WARNING: <script>: [DEV] - 1329ae2b-922d-4ae5-ade4-e1ed368c8bbc OPTIONS-17536 - in dialog and direction OUT, doing RELAY
2024-09-16T10:57:07+02:00 [1:nethvoice-proxy1:kamailio] e[0;39;49me[0;35;49m37(45) WARNING: <script>: [DEV] - 1329ae2b-922d-4ae5-ade4-e1ed368c8bbc OPTIONS-17536 - in RELAY route

And this is in the GUI:

But both IP’s are the same: etho: - x.x.x.x and x.x.x.x

This is a VPS with 1 Network card only.

Any idea’s please?
TIA

cc: @Amygos

Amygos · October 2, 2024, 2:04pm

This a bug NethVoice Proxy: IP check is wrong · Issue #7025 · NethServer/dev · GitHub, the fix has not already been released, but you can update to the testing release Release 1.0.2-testing.1 · nethesis/ns8-nethvoice-proxy · GitHub

Regardless the log flooding sadly is something that we have to improve in the next releases.

LayLow · October 3, 2024, 10:51pm

Is there a way to kill /limit the logging at this time, for the logfiles are ridiculous big and keep rotating. I have to delee the archves manually for they take up too much diskspace. It becomes a serious issue and logs are unreadable.

LayLow · October 5, 2024, 7:38pm

This is becoming a real issue for me, for the logs are unmanageable, unreadable and too way large. Also CRON is logging excessively with errors.

How can logging be stopped for now, unless turned on for debugging reasons. Both NethVoice and NethVoice-Proxy

LayLow · October 16, 2024, 8:56pm

Still looking at this. It seems that the kamailo config file (kamailio.cfg) is a bit confusing (double setting) containing this and next to that, not logging according set debug level.

# LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR
#!ifdef WITH_DEBUG
debug=4
log_stderror=yes
#!else
debug=1
log_stderror=no
#!endif

And the logfile contains zillions and zillions or WARNING log entries.

I rather have clear log levels, configurable in NethVoice-Proxy settings, with a reasonable default (like only errors being -1) . I ONLY need a deeper log level when I troubleshoot something with a trunk provider. I trust CrowdSec will efectively block hacking attempts at SIP level and those logs will tell me blocked hacking attempts.

cc @Amygos

LayLow · October 17, 2024, 1:31pm

Webtop is an excellent example of managing log levels and debugging