From owner-freebsd-bugs@freebsd.org Tue Jan 15 10:45:59 2019 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 806C01484F69 for ; Tue, 15 Jan 2019 10:45:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 17B7D816B1 for ; Tue, 15 Jan 2019 10:45:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id C620C1484F67; Tue, 15 Jan 2019 10:45:58 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1F4F1484F66 for ; Tue, 15 Jan 2019 10:45:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B991816AF for ; Tue, 15 Jan 2019 10:45:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 478ED1EE32 for ; Tue, 15 Jan 2019 10:45:57 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id x0FAjvZX088209 for ; Tue, 15 Jan 2019 10:45:57 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id x0FAjv5G088206 for bugs@FreeBSD.org; Tue, 15 Jan 2019 10:45:57 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 234968] syslogd remote logging doens't work (regression ?) Date: Tue, 15 Jan 2019 10:45:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: julien@perdition.city X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Jan 2019 10:45:59 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D234968 Bug ID: 234968 Summary: syslogd remote logging doens't work (regression ?) Product: Base System Version: 12.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: julien@perdition.city Created attachment 201159 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D201159&action= =3Dedit logging jail syslogd Hello, I have a JAIL (logging, 10.209.1.31) which is used as a centralized log hos= t. The JAIL and the HOST are running FreeBSD 12.0-RELEASE. The JAIL has an unmodified syslog.conf with one extra file in /usr/local/etc/syslog.d: root@logging:~ # ls -l /usr/local/etc/syslog.d total 5 -rw-r--r-- 1 root wheel 312 Jan 15 10:45 saltstack.conf root@logging:~ # cat /usr/local/etc/syslog.d/saltstack.conf=20 +router1.lan,router2.lan,router.lan local6.=3Dinfo /var/log/haproxy/http-access.log local6.=3Derr /var/log/haproxy/http-error.log local5.* /var/log/haproxy/smtp.log +dev.lan,antabif.lan,gitlab.lan,sandbox.lan,www1.prod.lan,www2.prod.lan local6.=3Dinfo /var/log/httpd/access.log local6.=3Derr /var/log/httpd/error.log DNS and reverse DNS are working properly. If I'm tcpdumping on the HOST everything look OK, packets are properly sent from remote hosts: root@HOST:~/ sudo tcpdump -n -i bge0 -p udp port 514 and host logging.lan Password: tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on bge0, link-type EN10MB (Ethernet), capture size 262144 bytes 11:31:37.273760 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 207 11:31:37.501015 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 208 11:31:38.074736 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local5.info, length: 151 11:31:38.501954 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 208 11:31:38.504479 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 205 11:31:38.586405 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 207 11:31:38.943227 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local5.info, length: 151 11:31:39.378678 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 177 11:31:39.500904 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 208 11:31:39.680232 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 177 11:31:39.694193 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 219 11:31:39.906661 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local5.info, length: 151 11:31:40.134680 IP 192.168.10.34.514 > 10.209.1.31.514: SYSLOG local6.error, length: 246 11:31:40.276486 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 207 11:31:40.494038 IP 192.168.10.34.514 > 10.209.1.31.514: SYSLOG local6.error, length: 246 11:31:40.501695 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 208 11:31:40.612300 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 241 11:31:40.745679 IP 10.209.1.252.43055 > 10.209.1.31.514: SYSLOG local6.info, length: 236 (...) I've launched syslogd in debug mode in the JAIL and as you can see syslog messages arrive properly to the syslogd (see attachment). For some unknown reasons nothing gets logged to /var/log/haproxy/*.log DNS and reverse DNS are working properly: root@logging:~ # host 10.209.1.252 252.1.209.10.in-addr.arpa domain name pointer router1.lan. root@logging:~ # host router1.lan router1.lan has address 10.209.1.252 syslogd on the HOST is binded to the HOST ip, files exist in /var/log/hapro= xy in the JAIL, etc: root@logging:~ # ls -l /var/log/haproxy/ total 2 -rw------- 1 root wheel 0 Jan 15 10:48 http-access.log -rw------- 1 root wheel 0 Jan 15 10:48 http-error.log -rw------- 1 root wheel 0 Jan 15 10:48 smtp.log Note that the same config worked in 10.4-RELEASE as expected and I'm out of ideas why it doesn't work on 12.0-RELEASE --=20 You are receiving this mail because: You are the assignee for the bug.=