Opened 5 months ago

Closed 3 weeks ago

#1281 closed Bug / Defect (wontfix)

OpenVPN Server logs timestamp format inconsistency

Reported by: jayals Owned by:
Priority: minor Milestone:
Component: Generic / unclassified Version: OpenVPN 2.4.8 (Community Ed)
Severity: Not set (select this one, unless your'e a OpenVPN developer) Keywords:
Cc:

Description

Server logs timestamp is having doublespace between Month and MonthDate? values. This is only true if MonthDate? is single digit dates (1-9). Issue here is if data is parsed through other log processing e.g. ELK timestamp format will be causing errors as format wont follow standard format e.g. "8EEE MMM dd HH:mm:ss uuuu"

Wed May  6 10:25:50 2020 us=55373 Re-using SSL/TLS context
Wed May  6 10:25:50 2020 us=55456 Control Channel MTU parms [ L:1623 D:1138 EF:112 EB:0 ET:0 EL:3 ]
Wed May  6 10:25:50 2020 us=55478 Data Channel MTU parms [ L:1623 D:1450 EF:123 EB:406 ET:0 EL:3 ]

Change History (2)

comment:1 Changed 3 weeks ago by Gert Döring

Milestone: alpha 2.4

"alpha 2.4" sounds like a really strange milestone... given that that release was like 4 years ago.

Please try the upcoming 2.5 version (2.5_beta2) has been released last week. It is using ISO timestamps for syslogging to file now.

Won't be changed for 2.4.x, though.

comment:2 Changed 3 weeks ago by Gert Döring

Resolution: wontfix
Status: newclosed

The 2.4 format does this on purpose, so that columns align nicely. If your parser cannot handle it, it needs to be adjusted. But we're not going to change this, as we moved to a different format in 2.5 anyway.

Note: See TracTickets for help on using tickets.