From owner-freebsd-ports-bugs@freebsd.org Fri May 4 08:14:05 2018 Return-Path: Delivered-To: freebsd-ports-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 0843BFCBA6D for ; Fri, 4 May 2018 08:14:05 +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 95D7C762BE for ; Fri, 4 May 2018 08:14:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 56CE6FCBA6C; Fri, 4 May 2018 08:14:04 +0000 (UTC) Delivered-To: ports-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 441D5FCBA6B for ; Fri, 4 May 2018 08:14:04 +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.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D3090762BA for ; Fri, 4 May 2018 08:14:03 +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 211647C43 for ; Fri, 4 May 2018 08:14:03 +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 w448E2a0091599 for ; Fri, 4 May 2018 08:14:03 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w448E2xN091598 for ports-bugs@FreeBSD.org; Fri, 4 May 2018 08:14:02 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: ports-bugs@FreeBSD.org Subject: [Bug 227965] net-mgmt/icinga2: using pkg/poudriere: wrong access right on crtical folders Date: Fri, 04 May 2018 08:14:02 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: ohartmann@walstatt.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: lme@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name 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-ports-bugs@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2018 08:14:05 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D227965 Bug ID: 227965 Summary: net-mgmt/icinga2: using pkg/poudriere: wrong access right on crtical folders Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: lme@FreeBSD.org Reporter: ohartmann@walstatt.org Assignee: lme@FreeBSD.org Flags: maintainer-feedback?(lme@FreeBSD.org) We update some servers of our infrastructure utilizing poudriere and pkg. I realized recently, that when using pkg with poudriere-built packages from o= ur repository, soemtimes the access rights of critical folders aren't set in t= he correct manner, resulting in a fail of restarting or even starting icinga2. In particular (my findings) those folders are: /var/cache/icinga2: it is set to root:icinga after an update, but should be icinga:icinga. Restart of icinga2 fails if not set correctly. /var/run/icinga2 and /var/run/icinga2/cmd: when module livestatus is enabled, the start of the service will fail, because, as mentioned before, the folders var/run/icinga2 and var/run/icinga2/cmd are owned by root and should be owned by icnga. Setting the correct access rights results in a normal operation of icinga2. --=20 You are receiving this mail because: You are the assignee for the bug.=