Your message dated Wed, 09 May 2012 21:29:38 +0200
with message-id <[email protected]>
and subject line Re: Bug#632543: cron job fails with "Authentication failure"
has caused the Debian Bug report #632543,
regarding cron job fails with "Authentication failure"
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
632543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632543
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debsecan
Version: 0.4.15
Severity: important
Hi,
After installing debsecan I never got mail from it.
Checking the logs I discovered that at the time of its cron job, cron
spits out "Authentication error".
There's no other cron job scheduled at that time in case you're
wondering.
Anything to do with it being run as daemon user?
Regards,
Raf
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.39-2-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages debsecan depends on:
ii debconf [debconf-2.0] 1.5.40 Debian configuration management sy
ii python 2.6.6-14 interactive high-level object-orie
ii python-apt 0.8.0 Python interface to libapt-pkg
Versions of packages debsecan recommends:
ii cron 3.0pl1-118 process scheduling daemon
ii dma [mail-transport-ag 0.0.2010.06.17-10 lightweight mail transport agent
debsecan suggests no packages.
-- debconf information:
* debsecan/source:
* debsecan/mailto: root
* debsecan/suite: sid
* debsecan/report: true
--- End Message ---
--- Begin Message ---
* Raf Czlonka:
> Recently I stumbled upon a similar problem witha another package [0].
> which I have managed to find a solution to.
> Luckily I did remember that I have seen it somehwere before and found
> out that it is affected by the same issue - the user was missing from
> shadow file (I should have checked it alongside passwd).
> Again, no idea how the user got removed though.
> One way or the other you can close this bug.
Thanks, closing.
--- End Message ---
