freebsd remote logging
julien at perdition.city
Tue Jan 15 10:09:49 UTC 2019
On Mon, Jan 14, 2019 at 04:22:46PM +0100, Julien Cigar wrote:
> I have a jail "logging" with the following configuration:
> for some unknown reasons nothing gets logged to /var/log/haproxy*.log,
> although the logs are received.
> When I'm adding -d flags to syslgod I'm getting the following:
> any idea what's wrong? I don't understand why the rule is
> matched/accepted but no "Logging to FILE" happens ..
> does something changed between 10.3 and 12.0 regarding this ?
this is really weird, I've tried everything and it doesn't work, is it
possible that there is some regression in the 12.0-RELEASE? the same
config worked in 10.4-RELEASE.
dns and reverse dns work are configured properly, tcpdumping the HOST
confirms that packets arrive as expected from the remote host (HAProxy),
launching the syslogd in the jail with -d confirms that messages arrive
and are parsed by syslogd but... nothing is logged to dedicated files
(except the ones from 11:01:25.185982 IP 192.168.10.34.514 >
10.209.1.31.514: SYSLOG local6.error, length: 246)
> Julien Cigar
> Belgian Biodiversity Platform (http://www.biodiversity.be)
> PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0
> No trees were killed in the creation of this message.
> However, many electrons were terribly inconvenienced.
Belgian Biodiversity Platform (http://www.biodiversity.be)
PGP fingerprint: EEF9 F697 4B68 D275 7B11 6A25 B2BB 3710 A204 23C0
No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: not available
More information about the freebsd-questions