[Logcheck-devel] Bug#312393: marked as done (logcheck: error creating lockfile.lock)

Wed Sep 21 21:18:21 UTC 2005

Your message dated Wed, 21 Sep 2005 23:03:55 +0200
with message-id <20050921210355.GB6480 at sputnik.stro.at>
and subject line Bug#312393: [Logcheck-devel] Bug#312393: logcheck: Some more information that might help
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 7 Jun 2005 22:02:00 +0000
>From peterwalser at yahoo.com Tue Jun 07 15:02:00 2005
Return-path: <peterwalser at yahoo.com>
Received: from 80-218-231-130.dclient.hispeed.ch (hal9000.aine.ch) [80.218.231.130] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1Dfm91-0005Mn-00; Tue, 07 Jun 2005 15:02:00 -0700
Received: by hal9000.aine.ch (Postfix, from userid 1000)
	id A0D1F36C38D; Wed,  8 Jun 2005 00:01:58 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Peter Walser <peterwalser at yahoo.com>
To: Debian Bug Tracking System <submit at bugs.debian.org>
Subject: logcheck: error creating lockfile.lock
X-Mailer: reportbug 3.8
Date: Wed, 08 Jun 2005 00:01:58 +0200
Message-Id: <20050607220158.A0D1F36C38D at hal9000.aine.ch>
Delivered-To: submit at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-4.3 required=4.0 tests=BAYES_00,FORGED_YAHOO_RCVD,
	HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: logcheck
Version: 1.2.39
Severity: important

Today I upgraded my server from woody to sarge.
After repeated installing and uninstalling of webmin (where logcheck is
used), I ended up with a version that does not work.

The directory for the lockfile.lock is not writable for the user logcheck.

SOLUTION:
After 'chown logcheck.users /var/lock/logcheck' it worked!

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (50, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages logcheck depends on:
ii  adduser          3.63                    Add and remove users and groups
ii  cron             3.0pl1-86               management of regular background p
ii  debconf [debconf 1.4.30.13               Debian configuration management sy
ii  debianutils      2.8.4                   Miscellaneous utilities specific t
ii  lockfile-progs   0.1.10                  Programs for locking and unlocking
ii  logcheck-databas 1.2.39                  A database of system log rules for
ii  logtail          1.2.39                  Print log file lines that have not
ii  mailx            1:8.1.2-0.20040524cvs-4 A simple mail user agent
ii  postfix [mail-tr 2.1.5-9                 A high-performance mail transport 
ii  sysklogd [system 1.4.1-17                System Logging Daemon

-- debconf information:
  logcheck/changes:
* logcheck/install-note:

---------------------------------------
Received: (at 312393-done) by bugs.debian.org; 21 Sep 2005 21:04:24 +0000
>From max at stro.at Wed Sep 21 14:04:24 2005
Return-path: <max at stro.at>
Received: from baikonur.stro.at [213.239.196.228] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1EIBlQ-0006Gm-00; Wed, 21 Sep 2005 14:04:24 -0700
Received: from sputnik (stallburg.stro.at [128.131.216.190])
	by baikonur.stro.at (Postfix) with ESMTP id 816AE5C00B;
	Wed, 21 Sep 2005 23:03:50 +0200 (CEST)
Received: from max by sputnik with local (Exim 4.52)
	id 1EIBkx-0002G1-D5; Wed, 21 Sep 2005 23:03:55 +0200
Date: Wed, 21 Sep 2005 23:03:55 +0200
From: maximilian attems <debian at sternwelten.at>
To: Ritesh Raj Sarraf <riteshsarraf at users.sourceforge.net>,
	312393-done at bugs.debian.org
Cc: Todd Troxell <ttroxell at debian.org>
Subject: Re: Bug#312393: [Logcheck-devel] Bug#312393: logcheck: Some more information that might help
Message-ID: <20050921210355.GB6480 at sputnik.stro.at>
References: <20050906195123.1F0B6C3165 at laptop.researchut-local.com> <20050907033407.GA9611 at rapidpacket.com> <200509071418.28352.riteshsarraf at users.sourceforge.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200509071418.28352.riteshsarraf at users.sourceforge.net>
User-Agent: Mutt/1.5.9i
X-Virus-Scanned: by Amavis (ClamAV) at stro.at
Delivered-To: 312393-done at bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02

> i guess you interrupt the postrm or similar to get into similar
> troubles.

unable to reproduce with normal purge and reinstall cycles.
a new install seemed to have cured the problems of the bug reporters.
as it appears only when interrupting the postinstall
closing this strange bug.

--
maks