Your message dated Tue, 6 Sep 2005 22:56:01 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#326837: leafnode: Unable to read config file after
dpkg-reconfigure
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; 6 Sep 2005 03:58:00 +0000
>From [EMAIL PROTECTED] Mon Sep 05 20:57:59 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail0.rawbw.com [198.144.192.41]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ECUat-0005wk-00; Mon, 05 Sep 2005 20:57:59 -0700
Received: from localhost (m201-14.dsl.tsoft.com [198.144.201.14])
by mail0.rawbw.com (8.11.6p2/8.11.6) with ESMTP id j863vxr19204;
Mon, 5 Sep 2005 20:57:59 -0700 (PDT)
Received: from ross by localhost with local (Exim 3.36 #1 (Debian))
id 1ECUar-0004ac-00; Mon, 05 Sep 2005 20:57:57 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Ross Boylan <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: leafnode: Unable to read config file after dpkg-reconfigure
X-Mailer: reportbug 3.15
Date: Mon, 05 Sep 2005 20:57:57 -0700
Message-Id: <[EMAIL PROTECTED]>
Sender: Ross Boylan <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Package: leafnode
Version: 1.11.3.rel-4
Severity: normal
I was running leafnode on a system with sporadic ppp connections.
After getting a permanent connection, I ran dpkg-reconfigure to tell
it I had one. Things didn't work after that, and the log show lots of
entries like
Sep 5 20:41:27 localhost leafnode[17504]: cannot open /etc/news/leafnode/config
Sep 5 20:41:27 localhost leafnode[17504]: 503 Unable to read configuration
file, exiting; the server's syslog should have more information.
All the files in /etc/news/leafnode/ had user and group of root.
It is possible this is an artifact of my editing the config file while
logged in as root (using RCS to control it). However, all the files
in the directory had root:root for owner:group.
I did a manual chgrp to news for those same files, and things seemed
to work after that.
So I may have caused the problem, but I thought I'd report it in case
not.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (990, 'stable'), (50, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.4.27advncdfs
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages leafnode depends on:
ii debconf [debconf-2.0] 1.4.57 Debian configuration management sy
ii libc6 2.3.5-6 GNU C Library: Shared libraries an
ii libpcre3 5.0-1.1 Perl 5 Compatible Regular Expressi
ii logrotate 3.7.1-1 Log rotation utility
ii netbase 4.21 Basic TCP/IP networking system
ii tcpd 7.6.dbs-8 Wietse Venema's TCP wrapper utilit
leafnode recommends no packages.
-- debconf information:
* leafnode/update-groups: false
leafnode/update-groupinfo:
* leafnode/tcpd: true
leafnode/update-maxcount:
leafnode/ppp:
* leafnode/network: permanent
leafnode/expireinfo:
leafnode/purge: false
* leafnode/server: nntp2.rawbw.com
---------------------------------------
Received: (at 326837-done) by bugs.debian.org; 6 Sep 2005 21:56:05 +0000
>From [EMAIL PROTECTED] Tue Sep 06 14:56:05 2005
Return-path: <[EMAIL PROTECTED]>
Received: from kerouac.projectcolo.org.uk [80.71.3.114]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1EClQD-00037d-00; Tue, 06 Sep 2005 14:56:05 -0700
Received: from localhost (localhost [127.0.0.1])
by kerouac.projectcolo.org.uk (Postfix) with ESMTP id C6ECD79D94
for <[EMAIL PROTECTED]>; Tue, 6 Sep 2005 22:56:03 +0100 (BST)
Received: from kerouac.projectcolo.org.uk ([127.0.0.1])
by localhost (kerouac [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 11030-05 for <[EMAIL PROTECTED]>;
Tue, 6 Sep 2005 22:56:03 +0100 (BST)
Received: from lorien.sirena.org.uk
(82-41-255-123.cable.ubr04.edin.blueyonder.co.uk [82.41.255.123])
(using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits))
(No client certificate requested)
by kerouac.projectcolo.org.uk (Postfix) with ESMTP id 8AB8679D39
for <[EMAIL PROTECTED]>; Tue, 6 Sep 2005 22:56:03 +0100 (BST)
Received: from raphaela (unknown [192.168.56.247])
by lorien.sirena.org.uk (Postfix) with ESMTP id 259EC2AD18
for <[EMAIL PROTECTED]>; Tue, 6 Sep 2005 22:56:02 +0100 (BST)
Received: by raphaela (Postfix, from userid 1000)
id 111B0FAA9B; Tue, 6 Sep 2005 22:56:01 +0100 (BST)
Date: Tue, 6 Sep 2005 22:56:01 +0100
From: Mark Brown <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Re: Bug#326837: leafnode: Unable to read config file after
dpkg-reconfigure
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-Cookie: Your step will soil many countries.
User-Agent: Mutt/1.5.10i
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at projectcolo.org.uk
Delivered-To: [EMAIL PROTECTED]
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
On Mon, Sep 05, 2005 at 08:57:57PM -0700, Ross Boylan wrote:
> All the files in /etc/news/leafnode/ had user and group of root.
> It is possible this is an artifact of my editing the config file while
> logged in as root (using RCS to control it). However, all the files
> in the directory had root:root for owner:group.
I can't reproduce this at all so I'll assume that it is as you suggest
a configuration error on your system. Only config needs to have
anything except root:root - it needs to be readable by user or group
news since it's not world readable due to the password.
--
"You grabbed my hand and we fell into it, like a daydream - or a fever."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
