RoyK, its been difficult to work on this as its not clear how to
reproduce yet. I'm wondering if this has to do with alternative
user/group sources like ldap and such. runlevel 2 happens before the
network is up, so calls to getent() for users that don't exist might
cause a failure. This would
We're seeing this on a number of servers. Starting cron manually after
bootup is obviously a solution, albeit obviously not really a good one.
Are anyone working on this at all???
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Evening, Clint.
I edited my cron.conf file as above to:
# cron - regular background program processing daemon
#
# cron is a standard UNIX program that runs user-specified programs at
# periodic scheduled times
description regular background program processing daemon
start on runlevel
Excerpts from Rob Rushworth's message of Fri Apr 29 16:03:20 UTC 2011:
Evening, Clint.
I edited my cron.conf file as above to:
# cron - regular background program processing daemon
#
# cron is a standard UNIX program that runs user-specified programs at
# periodic scheduled times
Happy to help.
I checked the whole of syslog back to January and see no mention of
cronlogger there either. Same for the whole daemon log.
Cron didn't run at boot after booting with the edited cron.conf file.
I removed the edit last night and booted again this morning. Cron not running
after
and attachment
** Attachment added: cron conf file edited boot syslog output after edit
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/592114/+attachment/2098073/+files/cron%20conf%20file%20edited%20boot%20syslog%20output%20after%20edit
--
You received this bug notification because
I think I may also have this problem.
Ubuntu 10.04 Lucid LTS 32bit.
Cron will now not start after boot-up, and as above, my box has had
several recent hard starts. I don't have console-tools though - I
already have KBD.
Yesterday, I managed to use the workaround boot / sudo cron stop / boot
.
Ok I'm marking it Confirmed because so many people have found that they
are affected.
Now we still need some help reproducing it. I'm wondering if we need to
change cron.conf to log crond's stdout/stderr.
If somebody who is affected could change /etc/init/cron.conf to remove
the 'expect fork'
Taking a look at this bug, and I'm wondering if there are any log
entries that could be helpful in determining why cron isn't running.
Could somebody who has experienced this please look through their log
files, especially /var/log/daemon.log and /var/log/syslog, for anything
from crond.
Also,
Looking in daemon.log from our last reboot, I see this:
Jan 27 02:00:00 dev1 init: cron main process (3627) killed by TERM
signal
And then during bootup, I see:
Jan 27 02:02:43 dev1 init: cron main process (1007) killed by TERM
signal
I don't have any syslog data right now because for some
We have a mix environment of Debian and Ubuntu and we use puppet for
configuration management. One of our recipes for Debian include console-
tools as a dependency. We reused that recipe in some of ours Ubuntu
Lucid 64 bit servers until we discovered that a group of services did
not start at boot
we solve the problem uninstalling console-tools package, it was breaking
upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/592114
Title:
upstart doesn't start cron automatically on boot in
I have similar problem with 32bit kubuntu lucid: cron doesn't running
after reboot
sudo service cron status
cron stop/waiting
chkconfig:
acpi-support off
acpid off
alsa-mixer-save off
anacron off
apparmor on
apport off
atd off
avahi-daemon off
binfmt-support on
bluetooth off
bootlogd off
This bug was reported on 2010-06-10 for an Ubuntu LTS release and since today
there is no fix released?
For me this means the latest LTS release is completely useless or is there a
fix available?
--
upstart doesn't start cron automatically on boot in lucid for server on amd64
I saw this on a fresh Lucid laptop install at some point after applying
security updates two weeks ago. Cron had not been running since 10 Sept
2010, and running sudo stop cron caused it to reappear on next boot.
This bug caused data backup jobs not to run, and could have been
disastrous.
--
Furthermore, this was on a 32-bit desktop (laptop, really) install, so
it may be worth amending the title of this bug to make it more generic
than amd64 server.
--
upstart doesn't start cron automatically on boot in lucid for server on amd64
https://bugs.launchpad.net/bugs/592114
You received
I have the problem, too. I have not found a workaround. I am running
10.04 on an AMD64 processor. It seems I'll have to drop back a version.
--
upstart doesn't start cron automatically on boot in lucid for server on amd64
https://bugs.launchpad.net/bugs/592114
You received this bug
I've got it too. Not tried the fix above as cannot turn machine (bog
standard Acer desktop with AMD processor) off at the moment.
--
upstart doesn't start cron automatically on boot in lucid for server on amd64
https://bugs.launchpad.net/bugs/592114
You received this bug notification because you
I appear to have this problem too, with cron not starting up at boot
since upgrade from Karmic to Lucid. (Well to be precise I noticed this a
couple of weeks after the upgrade after only sporadic use of the
machine, I don't know if it stopped working directly because of the
upgrade or stopped
David Scotson wrote:
Another common factor that might be affecting this is a number of hard-
resets and a series of power failures I experienced, which may have left
something in an awkward state.
I'm running the setup on a pair of IBM 3650s and the problem isn't with
just cron. Even my
See this thread: http://ubuntuforums.org/showthread.php?t=1479423
This bug affects a number of people. Based on having been able to get it
working I have a guess as to what the problem is. First, here is what I
did to get it working.
Cron wasn't starting through upstart but it would start by
Sorry, step 5 in the numbered list above should have been Reboot
--
upstart doesn't start cron automatically on boot in lucid for server on amd64
https://bugs.launchpad.net/bugs/592114
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
One more note (Launchpad should allow edits). This problem is only
upstart getting cron running on boot. I haven't had a problem with it
continuing to run after that.
--
upstart doesn't start cron automatically on boot in lucid for server on amd64
https://bugs.launchpad.net/bugs/592114
You
23 matches
Mail list logo
