From owner-freebsd-amd64@freebsd.org Fri Oct 28 18:18:21 2016 Return-Path: Delivered-To: freebsd-amd64@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9C3A2C2482E for ; Fri, 28 Oct 2016 18:18:21 +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 mx1.freebsd.org (Postfix) with ESMTPS id 72602EEB for ; Fri, 28 Oct 2016 18:18:21 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u9SIIL3f040573 for ; Fri, 28 Oct 2016 18:18:21 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 213859] /dev/pf device busy causes issues in complex systems Date: Fri, 28 Oct 2016 18:18:21 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 10.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: jjasen@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-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 cc 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-amd64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2016 18:18:21 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213859 Bug ID: 213859 Summary: /dev/pf device busy causes issues in complex systems Product: Base System Version: 10.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: jjasen@gmail.com CC: freebsd-amd64@FreeBSD.org CC: freebsd-amd64@FreeBSD.org Probably filed under pf: I have firewall systems using pf, with ftp_proxy as well. Under certain circumstances, relayd will crash when updating a table if something else (s= uch as ftp_proxy, tftp_proxy, or a local rules edit) has /dev/pf locked. I've seen other cases, where an individual ftp_proxy will also fail, if something else grabbed /dev/pf as well -- and seeing "pfctl: DIOCADDRULE: Device busy " failures when doing manual updates is quite common. relayd logs attached: Oct 28 17:26:15 fw-1/fw-1 relayd[31847]: table devproxy-http: 1 added, 0 deleted, 0 changed, 2 killed=20 Oct 28 17:26:15 fw-1/fw-1 relayd[31847]: fatal: sync_ruleset: cannot add address to pool: Device busy=20 Oct 28 17:26:15 fw-1/fw-1 kernel: Oct 28 17:26:15 pubgw2 relayd[31847]: fat= al: sync_ruleset: cannot add address to pool: Device busy=20 Oct 28 17:26:15 fw-1/fw-1 relayd[31848]: hce exiting, pid 31848 Oct 28 17:26:15 fw-1/fw-1 relayd[31849]: relay exiting, pid 31849 Oct 28 17:26:15 fw-1/fw-1 relayd[31851]: relay exiting, pid 31851 Oct 28 17:26:15 fw-1/fw-1 relayd[31852]: relay exiting, pid 31852 Oct 28 17:26:15 fw-1/fw-1 relayd[31854]: ca exiting, pid 31854 Oct 28 17:26:15 fw-1/fw-1 relayd[31853]: ca exiting, pid 31853 Oct 28 17:26:15 fw-1/fw-1 relayd[31850]: ca exiting, pid 31850 Oct 28 17:26:25 fw-1/fw-1 relayd[31846]: lost child: pfe exited abnormally= =20 Oct 28 17:26:25 fw-1/fw-1 kernel: Oct 28 17:26:25 pubgw2 relayd[31846]: lost child: pfe exited abnormally Oct 28 17:26:25 fw-1/fw-1 relayd[31846]: parent terminating, pid 31846 --=20 You are receiving this mail because: You are on the CC list for the bug.=