Re: How to add date/hour in Kamailio logs?

Henning Westerholt via sr-users <[email protected]>
Newsgroups gmane.comp.voip.ser
Message-ID <AM8PR07MB81088FACDDF2F08710DBED0FBFAAA@AM8PR07MB8108.eurprd07.prod.outlook.com>
Hello,

the log prefix will be not used for some error messages, as you correctly noticed.

One easy workaround is to just use a logging daemon like rsyslog and add the timestamp there before you route it to later processing steps.

Cheers,

Henning

--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com<https://gilawa.com/>


From: Benedito Marques via sr-users <[email protected]>
Sent: Montag, 15. Dezember 2025 22:23
To: Kamailio (SER) - Users Mailing List <[email protected]>
Cc: Benedito Marques <[email protected]>
Subject: [SR-Users] How to add date/hour in Kamailio logs?

It's possible to add date/hour or add more information in Kamailio logs?

I'm using kamailio inside containers. Even have an option in container manager (--timestamps in kubectl/docker for example), it's not possible to get some kamailio date/hour logs when using external logs tools like ELK.

I add this option to get date/hour in xlog:


log_prefix="[$Tf] - "


but some logs (like bellow) generated automatically by Kamailio have no this information:


Listening on
             tcp: 172.20.0.4:5091<http://172.20.0.4:5091> name tcp_socket advertise 200.200.200.200:5091<http://200.200.200.200:5091>
             tls: 172.20.0.4:5063<http://172.20.0.4:5063> name tls_socket advertise 200.200.200.200:5063<http://200.200.200.200:5063>
Aliases:
             tls: 2eab5fb54462:5063
             tcp: 2eab5fb54462:5091
 0(25) WARNING: tls [tls_init.c:807]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 204800 and 102400 bytes
16(41) ERROR: tls [tls_server.c:1329]: tls_h_read_f(): protocol level error
16(41) ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1408F09C:SSL routines:ssl3_get_record:http request
16(41) ERROR: tls [tls_server.c:1333]: tls_h_read_f(): source IP: 165.232.66.142
16(41) ERROR: tls [tls_server.c:1336]: tls_h_read_f(): destination IP: 172.20.0.4
16(41) ERROR: <core> [core/tcp_read.c:1479]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7fc51458ef30 r: 0x7fc51458f058 (-1)


--

Att,
Benedito Marques

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.