Description of problem: rsyslog should unify letter case and spaces in date in incoming messages: Version-Release number of selected component (if applicable): rsyslog-3.22.1-7.el5 How reproducible: always Steps to Reproduce: 1. configure rsyslogd to listen on port 514 2. Connect with netcat to port 514 # nc localhost 514 and send several messages such as <135>jun 4 09:03:41 dhcp-30-102 userx: local0.debug test message <134>JUN 4 09:03:49 dhcp-30-102 userx: local0.info test message <142>Jun 4 09:04:09 dhcp-30-102 userx: local1.info test message Then check that all messages were logged to /tmp/tcp.log and the case is unified (Jun 4) Actual results: Jul 25 05:16:39 localhost.localdomain jun 4 09:03:41 dhcp-30-102 userx: local0.debug test message Jul 25 05:16:39 localhost.localdomain JUN 4 09:03:49 dhcp-30-102 userx: local0.info test message Expected results: dates are in same format (Jun 4) Additional info: This is working fine on RHEL6.
When you say its working fine with RHEL6, does it mean its displaying date in "JUN 4" format? i.e. after unifying case? I used %TIMESTAMP% template with both the supported rfc's (3164,3339) & its displaying date in 2012-06-04 format only. I need this information so that I can take a call on whether to simply put toupper() in msgConstructWithTime() or check for RHEL-6 code changes (which I haven't come across yet).
Hi, on RHEL6 the date is displayed as "Jun 4", e.g. "Jun 4 09:03:41" note those 2 blank chars... day is probably ljustified to 2 characters, 'Jun 14' is converted to 'Jun 14'.
I feel below is the culprit in ParseTIMESTAMP3164() as it doesn't consider string as JUN, jun, juN etc. I will try to check with private build tomorrow whether after considering all cases it works or not. 338 case 'J': 339 if(*pszTS == 'a') { 340 ++pszTS; 341 if(*pszTS == 'n') { 342 ++pszTS; 343 month = 1; 344 } else 345 ABORT_FINALIZE(RS_RET_INVLD_TIME); 346 } else if(*pszTS == 'u') { 347 ++pszTS; 348 if(*pszTS == 'n') {
Created attachment 609946 [details] proposed patch Have verified and its working fine.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in the last planned RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX. To request that Red Hat re-consider this request, please re-open the bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.
I take it as no need to escalate, closing WONTFIX, as we are in production phase 3 in RHEL 5 and it works properly on RHEL 6.