Ubuntu
likewise-open5 package

@reboot local crontabs do not run for likewise-open5 domain users.

Bug #408947 reported by Tony Shadwick
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
likewise-open5 (Ubuntu)
Fix Released
Low
Thierry Carrez

Bug Description

Binary package hint: likewise-open5

I had likewise-open4 before upgrading to Jaunty, and this worked. Given the domain user shadwickt, I have jobs set in that user's crontab to run @reboot. That user does not have a local account on the system. At reboot, the following gets written to syslog:

Jul 31 10:11:41 shadwickt-desk /usr/sbin/cron[4269]: (CRON) STARTUP (fork ok)
Jul 31 10:11:41 shadwickt-desk /usr/sbin/cron[4269]: (shadwickt) ORPHAN (no passwd entry)
Jul 31 10:11:41 shadwickt-desk /usr/sbin/cron[4269]: (CRON) INFO (Running @reboot jobs)

That user's personal crontab gets skipped for @reboot jobs. Later crontabs do work.

likewise-open5's daemons (npcmuxd, dcerpcd, eventlogd, netlogond, and lsassd) start after cron. As a result, the user really does not exist to the system when cron first starts, thus the cron entry can't run @reboot.

To see why, do an ls of /etc/rc2.d. You'll note that cron has a symlink at S89, while the likewise daemons are at S91-S93.

The fix is simple, I changed my startup order in /etc/rc2.d through /etc/rc3.d so that it looks like this:

S85dcerpcd
S86eventlogd
S86netlogond
S86npcmuxd
S87lsassd

This is before both anacron and cron which are S89. Do that in all 4 of the rc directories listed, and reboot.

Revision history for this message
Thierry Carrez (ttx) wrote :

Thanks for reporting this and for the thorough analysis.

Changed in likewise-open5 (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Thierry Carrez (ttx)
Changed in likewise-open5 (Ubuntu):
assignee: nobody → Thierry Carrez (ttx)
status: Triaged → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package likewise-open5 - 5.0.3991.1+krb5-0ubuntu2

---------------
likewise-open5 (5.0.3991.1+krb5-0ubuntu2) karmic; urgency=low

  * debian/rules: Move likewise-open startup earlier in boot order to allow
    @reboot cronjobs to work (LP: #408947)

 -- Thierry Carrez <email address hidden> Fri, 18 Sep 2009 11:32:17 +0200

Changed in likewise-open5 (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Tony Shadwick (numbski+bugs-launchpad-net) wrote :

Sadly, this bug needs to be re-opened due to the advent of Karmic Koala and the Upstart system. Once again, likewise-open5 is starting LONG after cron runs. Or is this a situation where the likewise-open5 package just needs to be reinstalled to properly use upstart?

As it stands, gdm starts long before lsassd is running, and as a result for the first minute or so you cannot log in.

Changed in likewise-open5 (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Thierry Carrez (ttx) wrote :

Please don't reopen fixed bugs.
Your issue is a new bug (introduced by upstartification of gdm), with the same symptoms. It needs a different fix (probably upstartification of likewise-open5 init script). Please file a new, separate bug.

Changed in likewise-open5 (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Tony Shadwick (numbski+bugs-launchpad-net) wrote :

Created the new bug:

https://bugs.launchpad.net/ubuntu/+source/likewise-open/+bug/605123

Cross-posting here because it seems the same people aren't being notified?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.