Your message dated Tue, 28 Feb 2023 15:13:40 +0000
with message-id <[email protected]>
and subject line Bug#1032123: Removed package(s) from unstable
has caused the Debian Bug report #308904,
regarding Cron forget to fire jobs
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.)
--
308904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=308904
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Package: cron
Version: 3.0pl1-87
Severity: normal
I'm not absolutely sure if this is not related to #206948. But on my
environment cron is not dieing it just stop running jobs.
I notice it several days ago when I got no more mails from one maschine.
It seems that from one time to another cron stops executing jobs. A
Restart of cron fixes the problem but now two days later the same
happens again.
Just when I wrote this mail I found that there was 1400 cron jobs
running.
- -- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (800, 'unstable'), (700, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.30
Locale: LANG=de_DE, LC_CTYPE=de_DE (charmap=ISO-8859-1) (ignored: LC_ALL set to
de_DE)
Versions of packages cron depends on:
ii adduser 3.63 Add and remove users and groups
ii debianutils 2.13.2 Miscellaneous utilities specific t
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
ii libpam0g 0.76-22 Pluggable Authentication Modules l
- -- no debconf information
- --
Klaus Ethgen http://www.ethgen.de/
pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <[email protected]>
Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iQEVAwUBQoRNt5+OKpjRpO3lAQI7nQf9ExbuAtxOJ+p9bFIShWHIeG8dteHRAXWx
4cO6upmz9uUjdVtcMacHFgBOQLbkDs8UyqTyprB3n9K1NWfOfvjFtw6ffTf7IScx
L0TqO8zMdLqKBoRFYVLm5hWtRSZj+1cyu2jK5G5Tx5IWyVcMdW1O3OAsBUXvQcYt
d4OLFUFNCYkdf1DJrq10hqMl7R9kZpoKIo/yS5XzZ9VjlUnVVZrfhOL02Mr7/qvA
m50OvWsMfH2dXq1fhuXE5V+h5CVmAYupBsnSWsfKtr0Lg9hIe6PywHss6/kxb/jB
YJeAz1qMlk8sxFNpb+Vo+fj+Po9XnMSEzWxIkKD0ejxXxW/LsVI0nA==
=RPCF
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Version: 186-4.1+rm
Dear submitter,
as the package libpam-ldap has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1032123
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
