Date: Fri, 4 Jan 2019 08:26:34 +1100 From: Ben Woods <woodsb02@gmail.com> To: Matt Churchyard <matt.churchyard@userve.net>, "ed@freebsd.org" <ed@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: FreeBSD 12 log formats Message-ID: <CAOc73CCaKQvzvVFXS-5OTE3d91y37N897b6rwtccZmokzicTLA@mail.gmail.com> In-Reply-To: <0478636f9afd49d68a7d0c86d68c01e3@SERVER.ad.usd-group.com> References: <0478636f9afd49d68a7d0c86d68c01e3@SERVER.ad.usd-group.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 3 Jan 2019 at 3:12 am, Matt Churchyard <matt.churchyard@userve.net> wrote: > I (and other users) have noticed that log messages have started appearing > in a different format in FreeBSD 12 (although in my case only on one > system, and some logs are still the original format...). > ... > > Jan 2 12:04:13 ftp 1 2019-01-02T12:04:13.584377+00:00 ftp.full.hostname > pkg 5522 - - php72-hash-7.2.13 installed > Hi Matt, That log message has both the old and new formats combined - I believe that will occur when you are using an old syslog daemon with the new libc syslog(3) code. By =E2=80=9Cold=E2=80=9D daemon, I mean one that has not be= en updated to expect the /var/run/log[priv] sockets to contain RFC5424 style logs. Are there any jails involved with the above log message, or was it simply running =E2=80=9Cpkg install ...=E2=80=9D on the FreeBSD 12 host? If you are using rsyslog or syslog-ng, the UPDATING entry for this change (linked below) includes instructions required to make them work with the new libc code: https://svnweb.freebsd.org/base/head/UPDATING?r1=3D332100&r2=3D332099&pathr= ev=3D332100 Regards, Ben --=20 -- From: Benjamin Woods woodsb02@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOc73CCaKQvzvVFXS-5OTE3d91y37N897b6rwtccZmokzicTLA>