syslog-ng: Time zone information is incorrect on the wire
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @BKPepe
Environment: merge-base with openwrt/master is commit 90e4c8c6e6 Date: Mon May 23 21:05:59 2022 +0200
Hardware happens to be multiple EA8300 units. Problem observed with OpenWrt, Debian, and FreeBSD log hosts.
Using syslog-ng with an expanded version of the supplied configuration that includes remote logging. Whether using the BSD-style or "modern" syslog (RFC 5424) transport, the time zone and time are inconsistent. The receiver reports what appears to be UTC time with the local time zone offset, presently -0700.
Examining the RFC 5424 packets on the wire confirms that the incorrect timestamp is present.
Looking at the packet on the wire, at 21:03:49 local time (Pacific)
<27>1 2022-05-30T04:03:49-07:00 front hostapd - - [meta sequenceId="27"] nl80211: kernel reports: key addition failed
Local date is correct
jeff@front:/etc$ date
Sun May 29 21:08:39 PDT 2022
jeff@front:/etc$ uci get system.@system[0].timezone
PST8PDT,M3.2.0,M11.1.0
To replicate:
- Configure a log host that accepts RFC5424 logging
- Add the following, tailored to your log host's IP address, as
/etc/syslog-ng.d/d_remote.confon the OpenWrt device
destination d_remote {
syslog("10.11.12.13" transport(tcp));
};
log {
source(kernel);
source(src);
source(net);
destination(d_remote);
};
sudo service syslog-ng restartor similar on the OpenWrt device
Previous references:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue using /etc/syslog-ng.d/d_remote.conf, the supplied syslog-ng configuration, and an RFC 5424 log host; inspect the timestamp on the wire after restarting syslog-ng. Done means the transmitted time and timezone offset agree with the OpenWrt device's local date and configured timezone.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100