Pawel Konieczny
2004-Nov-07 13:17 UTC
[Logcheck-devel] Bug#280125: pam fails on su logcheck command in the crontab
Package: logcheck Version: 1.2.28 Severity: minor logcheck installs the following line (or similar) in the root crontab: 2 * * * * if [ -x /usr/sbin/logcheck ]; then su -s /bin/bash -c "nice -n10 /usr/sbin/logcheck" logcheck; fi However, su reports pam authentication error (mailed to root): su: Authentication service cannot retrieve authentication info. (Ignored) The problem is that the installation script of logcheck, when creating the user "logcheck" did not create the corresponding entry in /etc/shadow An entry in /etc/shadow like this would fix it: logcheck:!:12729:0:99999:7:::
Todd Troxell
2004-Nov-07 21:20 UTC
Bug#280125: [Logcheck-devel] Bug#280125: pam fails on su logcheck command in the crontab
On Sun, Nov 07, 2004 at 02:17:19PM +0100, Pawel Konieczny wrote:> The problem is that the installation script of logcheck, when creating the user "logcheck" did not create the corresponding entry in /etc/shadowThis is strange because we use adduser which adds entries to both files. Is it possible that the installation was interrupted? Is your adduser program functional? When you purge and re-install logcheck, is it still missing from shadow? Thanks, -- [ Todd J. Troxell ,''`. Student, Debian GNU/Linux Developer, SysAdmin, Geek : :' : http://debian.org || http://rapidpacket.com/~xtat `. `' `- ] -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://lists.alioth.debian.org/pipermail/logcheck-devel/attachments/20041107/11a79c3d/attachment.pgp
maks attems
2004-Nov-10 11:23 UTC
Bug#280125: [Logcheck-devel] Bug#280125: pam fails on su logcheck command in the crontab
On Sun, 07 Nov 2004, Pawel Konieczny wrote:> logcheck installs the following line (or similar) in the root crontab: > 2 * * * * if [ -x /usr/sbin/logcheck ]; then su -s /bin/bash -c "nice -n10 /usr/sbin/logcheck" logcheck; fi > > However, su reports pam authentication error (mailed to root): > su: Authentication service cannot retrieve authentication info. > (Ignored) > > The problem is that the installation script of logcheck, when creating the user "logcheck" did not create the corresponding entry in /etc/shadow > > An entry in /etc/shadow like this would fix it: > logcheck:!:12729:0:99999:7:::are you using debian? (version) or did you an cvs checkout and make install? thanks for further infos on the system of your box? -- maks
maximilian attems
2004-Nov-11 09:23 UTC
Bug#280125: [Logcheck-devel] Bug#280125: pam fails on su logcheck command in the crontab
please do not forget to cc your bug report! On Thu, 11 Nov 2004, Pawel Konieczny wrote:> I have purged logcheck and installed it again. > I have noticed that --purge did not remove the logcheck entries from the root crontab (crontab -l). > It also did not remove /etc/logcheck and subdirectories. > It did remove /var/log and all subdirectories!!! > Installing logcheck again created a new file /etc/cron.d/logcheck > Also the user logcheck has been added correctly. > > I have installed logcheck long time ago, then removed it (not purged) and then installed again. So probably the current logcheck does not have any problems, if it is not reproducible. Please check pruning /var/log issue. > > //Pawelok i'll double check that soon, but i guess you are speeking of /var/lib/logcheck. logcheck has no way to rm /var/log! -- maks
Debian Bug Tracking System
2004-Nov-11 21:18 UTC
[Logcheck-devel] Bug#280125: marked as done (pam fails on su logcheck command in the crontab)
Your message dated Thu, 11 Nov 2004 22:03:13 +0100 with message-id <20041111210312.GA2017 at stro.at> and subject line Bug#280125: [Logcheck-devel] Bug#280125: pam fails on su logcheck command in the crontab 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 Nov 2004 13:18:12 +0000>From konieczp at users.sourceforge.net Sun Nov 07 05:18:12 2004Return-path: <konieczp at users.sourceforge.net> Received: from dslam145-152-59-81.dyndsl.zonnet.nl (almaden.alsacenet.nl) [81.59.152.145] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CQmvr-0003yz-00; Sun, 07 Nov 2004 05:18:12 -0800 Received: from [192.168.0.13] (helo=NLYEHVDSL1W9030) by almaden with smtp (Exim 4.34) id 1CQmvH-000476-2J for submit at bugs.debian.org; Sun, 07 Nov 2004 14:17:35 +0100 Message-ID: <001b01c4c4cc$22f28c70$0d00a8c0 at nlyehvdsl1ad.ehv.pdsl.philips.com> From: "Pawel Konieczny" <konieczp at users.sourceforge.net> To: <submit at bugs.debian.org> Subject: pam fails on su logcheck command in the crontab Date: Sun, 7 Nov 2004 14:17:19 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Delivered-To: submit at bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-5.1 required=4.0 tests=BAYES_44,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: logcheck Version: 1.2.28 Severity: minor logcheck installs the following line (or similar) in the root crontab: 2 * * * * if [ -x /usr/sbin/logcheck ]; then su -s /bin/bash -c "nice -n10 /usr/sbin/logcheck" logcheck; fi However, su reports pam authentication error (mailed to root): su: Authentication service cannot retrieve authentication info. (Ignored) The problem is that the installation script of logcheck, when creating the user "logcheck" did not create the corresponding entry in /etc/shadow An entry in /etc/shadow like this would fix it: logcheck:!:12729:0:99999:7::: --------------------------------------- Received: (at 280125-done) by bugs.debian.org; 11 Nov 2004 21:03:24 +0000>From max at stro.at Thu Nov 11 13:03:24 2004Return-path: <max at stro.at> Received: from baikonur.stro.at [213.239.196.228] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CSM6F-0005f1-00; Thu, 11 Nov 2004 13:03:24 -0800 Received: from localhost (localhost [127.0.0.1]) by baikonur.stro.at (Postfix) with ESMTP id 082345C00B; Thu, 11 Nov 2004 22:03:20 +0100 (CET) Received: from baikonur.stro.at ([127.0.0.1]) by localhost (baikonur [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28069-04; Thu, 11 Nov 2004 22:03:12 +0100 (CET) Received: from sputnik (stallburg.stro.at [128.131.216.190]) by baikonur.stro.at (Postfix) with ESMTP id D83E95C00A; Thu, 11 Nov 2004 22:03:11 +0100 (CET) Received: from max by sputnik with local (Exim 4.34) id 1CSM65-0000jg-61; Thu, 11 Nov 2004 22:03:13 +0100 Date: Thu, 11 Nov 2004 22:03:13 +0100 From: maks attems <debian at sternwelten.at> To: 280125-done at bugs.debian.org Cc: Todd Troxell <ttroxell at debian.org> Subject: Re: Bug#280125: [Logcheck-devel] Bug#280125: pam fails on su logcheck command in the crontab Message-ID: <20041111210312.GA2017 at stro.at> References: <001b01c4c4cc$22f28c70$0d00a8c0 at nlyehvdsl1ad.ehv.pdsl.philips.com> <20041110112317.GD889 at stro.at> <003601c4c77a$b8a75c90$0d00a8c0 at nlyehvdsl1ad.ehv.pdsl.philips.com> <20041111092314.GA6515 at stro.at> <20041111181406.GE2660 at stro.at> <001a01c4c826$4af2e000$0d00a8c0 at nlyehvdsl1ad.ehv.pdsl.philips.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001a01c4c826$4af2e000$0d00a8c0 at nlyehvdsl1ad.ehv.pdsl.philips.com> User-Agent: Mutt/1.5.6+20040722i Sender: maximilian attems <max at stro.at> X-Virus-Scanned: by Amavis (ClamAV) at stro.at Delivered-To: 280125-done at bugs.debian.org X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: On Thu, 11 Nov 2004, Pawel Konieczny wrote:> I have retested the installation and removal of logcheck sereval times. There is no trace of any irregularities (also no /var/log issue anymore). There was probably something wrong with my past installation. Please close my report./me prefers working logcheck. ok thanks anyway for feedback and double-check. closing this bugreport. feel free to open another one, if you find other issues. regards maks