I noticed this error on Ubuntu 20.10. Local OpenLDAP, nslcd and a LDAP-
user's cron-jobs aren't run because the log says orphaned.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
This problem is still *not* fixed.
(I am running cron 3.0pl1-116ubuntu1 on 11.04 with users in NIS.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches
So what's the status on this one? Are we good to go?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing
This bug was fixed in the package cron - 3.0pl1-106ubuntu6
---
cron (3.0pl1-106ubuntu6) lucid-proposed; urgency=low
* Cherry-pick fix from Debian: database.c, cron.c, cron.h
:
- Check orphaned crontabs for adoption. Fix taken from Fedora cronie.
Closes: #634926, LP:
Sorry, as previous comments have mentioned, the timeline to get this
fixed means all of my affected systems have been migrated to other
distros / authentication methods / workarounds in the intervening 6
years. I've actually switched jobs twice since this bug was opened, and
the place I work now
** Branch linked: lp:ubuntu/lucid-proposed/cron
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
message and
I don't consider it appropriate to fix this in maverick or natty.
maverick is two months before its EOL, and given the regression
potential of such a central package and service I don't see us ever
getting enough testing for natty either.
The SRU upload for lucid changes debian/copyright, why is
Hi Martin, the debian commit including the patch from Tomas Mraz (cronie
fedora) included the copyright changes. Perhaps a cleanup. We decided to
keep it consistent, should we remove these? thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Jose Plans [2012-02-28 14:02 -]:
Hi Martin, the debian commit including the patch from Tomas Mraz (cronie
fedora) included the copyright changes. Perhaps a cleanup. We decided to
keep it consistent, should we remove these? thanks
They don't hurt much either way, but it's very unusual to
Well... I don't seriously mind not fixing maverick, but reject changes
for natty more than half a year before EOL as you will, just don't
expect that this raises credibility of Ubuntu support.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Matthias, to Martin's point, the level of testing we see in each release
goes down significantly as new stable releases are available. This is
evident in the number of untested SRU's that have been pushed into
natty-proposed and stayed there because not even the original reporters
return to verify
Am 28.02.2012 20:55, schrieb Clint Byrum:
Matthias, to Martin's point, the level of testing we see in each release
goes down significantly as new stable releases are available. This is
evident in the number of untested SRU's that have been pushed into
natty-proposed and stayed there because
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
message and skipping jobs
** Branch linked: lp:~barry/ubuntu/maverick/cron/bug-27520
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
** Branch linked: lp:~barry/ubuntu/lucid/cron/bug-27520
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
** Branch linked: lp:~barry/ubuntu/natty/cron/bug-27520
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
I'm changing the version number for the natty SRU to 3.0pl1-116ubuntu1.1
since otherwise, you have the potential (should another upload to natty
be required) of running into the oneric version number. If that
happens, people upgrading from natty to oneiric could potentially miss
the oneiric
All three uploads are sponsored now.
** Changed in: cron (Ubuntu Lucid)
Status: In Progress = Fix Committed
** Changed in: cron (Ubuntu Maverick)
Status: In Progress = Fix Committed
** Changed in: cron (Ubuntu Natty)
Status: In Progress = Fix Committed
** Changed in: cron
** Changed in: cron (Ubuntu Lucid)
Assignee: (unassigned) = Barry Warsaw (barry)
** Changed in: cron (Ubuntu Maverick)
Assignee: (unassigned) = Barry Warsaw (barry)
** Changed in: cron (Ubuntu Natty)
Assignee: (unassigned) = Barry Warsaw (barry)
--
You received this bug
** Changed in: cron (Ubuntu Lucid)
Status: Triaged = In Progress
** Changed in: cron (Ubuntu Maverick)
Status: Triaged = In Progress
** Changed in: cron (Ubuntu Natty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Ubuntu
** Patch removed: cron_3.0pl1-106ubuntu5~LP27520.lucid.debdiff
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/27520/+attachment/2592049/+files/cron_3.0pl1-106ubuntu5%7ELP27520.lucid.debdiff
** Patch removed: cron_3.0pl1-114ubuntu1.LP27520.maverick.debdiff
** Patch added: natty-proposed.debdiff
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/27520/+attachment/2682612/+files/cron_3.0pl1-116ubuntu2.natty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
** Patch added: debdiff with proper versioning and updated copyright
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/27520/+attachment/2682610/+files/cron_3.0pl1-106ubuntu6.lucid.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Patch added: maverick-proposed.debdiff
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/27520/+attachment/2682611/+files/cron_3.0pl1-114ubuntu2.maverick.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Lucid's debdiff
** Description changed:
+ == SRU Justification ==
+
+ * Impact: users being defined on remote user databases such as LDAP will
+ not be able to access to their cron jobs and these will be marked as
+ orphaned unless cron is restarted. The impact is severe for users
+ relying on
Maverick's debdiff
** Patch added: cron_3.0pl1-114ubuntu1.LP27520.maverick.debdiff
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/27520/+attachment/2592050/+files/cron_3.0pl1-114ubuntu1.LP27520.maverick.debdiff
--
You received this bug notification because you are a member of Ubuntu
Natty's debdiff
** Patch added: cron_3.0pl1-116ubuntu1.LP27520.natty.debdiff
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/27520/+attachment/2592051/+files/cron_3.0pl1-116ubuntu1.LP27520.natty.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Also affects: cron (Ubuntu Maverick)
Importance: Undecided
Status: New
** Also affects: cron (Ubuntu Natty)
Importance: Undecided
Status: New
** Changed in: cron (Ubuntu Maverick)
Status: New = Triaged
** Changed in: cron (Ubuntu Maverick)
Status: Triaged =
This bug has been incorrectly marked as fixed for the most recent
development release due to the addition of Should-Start: nslcd to the
init script. A more complete fix is still needed here.
** Changed in: cron (Ubuntu)
Status: Fix Released = Triaged
--
You received this bug
uploaded the Debian fix to the freeze queue for oneiric. Once accepted,
this can be backported to lucid.
** Changed in: cron (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
** Branch linked: lp:ubuntu/cron
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
message and skipping jobs
This bug was fixed in the package cron - 3.0pl1-116ubuntu3
---
cron (3.0pl1-116ubuntu3) oneiric; urgency=low
* Cherry-pick fix from Debian: database.c, cron.c, cron.h,
debian/copyright:
- Check orphaned crontabs for adoption. Fix taken from Fedora cronie.
Closes:
Any chance for a fix in Lucid on this one?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
message and
cron 3.0pl1-119, recently uploaded to Debian unstable, contains a patch
that forces a rescan of ORPHANed crontabs. Credit for the fix goes to
Fedora cronie, from where it was taken.
I'll try to get this sync'ed over the weekend, together with some other
bugfixes for cron in Ubuntu.
--
You
** Changed in: cron (Ubuntu Lucid)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing
Am 18.06.2011 03:39, schrieb Christian Kastner:
As I mentioned earlier, I have a fix in mind for the next release which
should resolve the issue in a manner not conflicting with the other goals.
next release doesn't help those running LTS...
--
Matthias Andree
--
You received this bug
On 06/18/2011 11:29 AM, Matthias Andree wrote:
Am 18.06.2011 03:39, schrieb Christian Kastner:
As I mentioned earlier, I have a fix in mind for the next release which
should resolve the issue in a manner not conflicting with the other goals.
next release doesn't help those running LTS...
As
** Changed in: cron (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup results, causing ORPHAN
On 06/08/2011 12:30 AM, Nathan Stratton Treadway wrote:
In the longer term, obviously it would be great for cron better
integrate with network-based user databases, but it would be nice to
hear from some Ubuntu developers whether that sort of change is likely
to get backported to Lucid?
This
On 06/08/2011 01:52 AM, Graeme wrote:
Regardless, it's been my experience that Ubuntu doesn't backport fixes
of this nature to releases that have already shipped. I've found that
the bugs must constitute a clear, widespread problem for a majority of
users before a backport is even considered.
On 06/08/2011 11:12 AM, Matthias Andree wrote:
Am 08.06.2011 01:17, schrieb Christian Kastner:
Theoretically, this could easily be extended to #27520 -- just a few
lines of code, actually -- but it's just not that simple, because there
are cases where ORPHAN is completely valid, ie the user
On 06/08/2011 11:14 AM, Matthias Andree wrote:
- it often takes longer than a year for a bug report to be triaged at
all, not even thinking of looked at by the packagers -- even for
things that are clearly upstream bugs and need to be delegated outside
Ubuntu, which doesn't require packager
** Also affects: cron (Ubuntu Lucid)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27520
Title:
cron daemon caches user-non-existent lookup
You can achieve such a workaround, but it's prone to races and
unreliable. Better to fix cron and stop it from caching which user
exists or not.
My lucid /etc/init/cron.conf for NIS currently looks as given below, and
tested on some old-fashioned Pentium 4 HT computer that suffered
heavily,
Am 08.06.2011 01:17, schrieb Christian Kastner:
Theoretically, this could easily be extended to #27520 -- just a few
lines of code, actually -- but it's just not that simple, because there
are cases where ORPHAN is completely valid, ie the user really doesn't
exist.
Fine, but cron should
I'd concur with Graeme's observations:
- it often takes longer than a year for a bug report to be triaged at
all, not even thinking of looked at by the packagers -- even for
things that are clearly upstream bugs and need to be delegated outside
Ubuntu, which doesn't require packager attention
** Summary changed:
- cron daemon starts before LDAP/NIS client, causing ORPHAN message for all
LDAP/NIS-defined users
+ cron daemon caches user-non-existent lookup results, causing ORPHAN message
and skipping jobs for all LDAP/NIS-defined users
--
You received this bug notification because
Note there may be two separate fixes involved here (for Lucid, at least;
not sure about Maverick)
In the short term, how can we once-again tweak the startup scripts so
that cron is always started after nslcd/nis/likewise-open/whatever has
already started (especially if the other damon in question
Nathan: I think that since this bug sat untouched from 2005-2010, you
can guess that the answer is going to be No, don't care. I'm just
happy if a fix eventually makes into some Ubuntu release at some point
in the /next/ 5 years.
--
You received this bug notification because you are a member of
On 06/08/2011 12:53 AM, Graeme wrote:
Nathan: I think that since this bug sat untouched from 2005-2010, you
can guess that the answer is going to be No, don't care.
If you look at the changelog for recent versions of cron, you can see
that somebody does care for bug reports.
I'm just happy if
Christian: Sorry, I was being a little facetious. Yes, the recent
traffic on this bug indicates things have changed with regards to these
kinds of issues. That being said, it did take 5 years for anyone to
bother looking into it. Forgive me if I'm a little pessimistic about the
speed with which
52 matches
Mail list logo
