From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/2633 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Laurent Bercot" Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: A better method than daisy-chaining logging files? Date: Mon, 17 Jun 2019 17:58:39 +0000 Message-ID: References: <16c909e2-9b84-63c8-7c60-380befe28f01@heuristicsystems.com.au> <8447f17e-0960-196d-bdf5-64a3d203cff0@heuristicsystems.com.au> Reply-To: "Laurent Bercot" Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="256935"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: eM_Client/7.2.34711.0 To: "supervision@list.skarnet.org" Original-X-From: supervision-return-2223-gcsg-supervision=m.gmane.org@list.skarnet.org Mon Jun 17 19:57:44 2019 Return-path: Envelope-to: gcsg-supervision@m.gmane.org Original-Received: from alyss.skarnet.org ([95.142.172.232]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hcvsz-0014gR-Lo for gcsg-supervision@m.gmane.org; Mon, 17 Jun 2019 19:57:41 +0200 Original-Received: (qmail 26464 invoked by uid 89); 17 Jun 2019 17:58:05 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Original-Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Original-Received: (qmail 26457 invoked from network); 17 Jun 2019 17:58:05 -0000 In-Reply-To: <8447f17e-0960-196d-bdf5-64a3d203cff0@heuristicsystems.com.au> X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduuddrudeijedguddulecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfpfgfogfftkfevteeunffgpdfqfgfvnecuuegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhhrfgggtgfgsehtqhertddtreejnecuhfhrohhmpedfnfgruhhrvghnthcuuegvrhgtohhtfdcuoehskhgrqdhsuhhpvghrvhhishhiohhnsehskhgrrhhnvghtrdhorhhgqeenucfrrghrrghmpehmohguvgepshhmthhpohhuthenucevlhhushhtvghrufhiiigvpedt Xref: news.gmane.org gmane.comp.sysutils.supervision.general:2633 Archived-At: ># s6-svc -a /run/scan/apache24-error-log > >The result is a directory containing >-rw-r--r-- 1 mylogger www 0B Jun 17 15:34 state >-rw-r--r-- 1 mylogger www 0B Jun 17 15:34 lock >-rwxr--r-- 1 mylogger www 329B Jun 17 15:34 previous >-rw-r--r-- 1 mylogger www 0B Jun 17 15:34 current > >and an error message >s6-log: warning: unable to finish previous .s to logdir >/var/log/httpd/error: Operation not permitted > >I've su'ed into the /var/log/httpd/error as "logger" and I'm able to >create and compress files within the directory; so there are no >permission issues. And both execlineb and s6-log are installed with 766 >privs. You mean "mylogger", I assume? Does the mylogger user belong to the www group? What are the permissions on the /var/log/httpd/error directory itself? Can you send a strace, or a kdump/ktrace, of the s6-log process when the error occurs? One of the system calls performed during a rotation is failing with EPERM and knowing which one will help us pinpoint exactly what's going wrong. >Does s6-log require root:wheel privs to perform functions within the log >directory? No, if the logdir belongs to the user s6-log is running as, and has at least S_IRWXU permissions, then s6-log is good to go. Something else is going on here, and knowing what syscall is failing will tell us where to look. -- Laurent