Hi Stuart,
Note that Anacron is not a daemon; it needs to be executed at boot time
and intermittently thereafter (via that cron.d script).
It doesn't work to have Anacron run only at boot time and Cron
thereafter, because Anacron maintains state in /var/spool/anacron/ that
needs to be updated eac
The default /etc/anacrontab only executes cron jobs, doesn't this make
/etc/cron.d/anacron unnecessary?
Boot time execution of anacron (/etc/init.d/anacron) takes care of jobs
missed while the PC was off and cron takes care of things while the PC
is on.
--
You received this bug notification bec
I got the email last time I rebooted:
Delivered-To: ptomb...@gmail.com
Received: by 10.70.54.225 with SMTP id m1csp509715pdp;
Thu, 21 May 2015 04:30:03 -0700 (PDT)
X-Received: by 10.140.19.108 with SMTP id 99mr2819447qgg.56.1432207802871;
Thu, 21 May 2015 04:30:02 -0700 (PDT)
Retur
It affects me too (mythbuntu thrusty x64).
Description:Ubuntu 14.04.2 LTS
Release:14.04
anacron:
Installiert: 2.3-20ubuntu1
Installationskandidat: 2.3-20ubuntu1
Versionstabelle:
*** 2.3-20ubuntu1 0
500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packag
This bug affect me, Kubuntu 14.04 x64.
I've wake up my machine at 7:30, after suspend.
de "root"
à root@unspecified-domain
date15/08/14 07:30
objet Cron start -q anacron || :
start: Job is already running: anacron
--
You received this bug notification because you are a member
This is a long living bug and it is quite disruptive. It is affecting me on..
$ . /etc/os-release
$ echo $VERSION
14.04, Trusty Tahr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606491
Title:
start
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606491
Title:
start:
I said I observed the bug on 14.04, also happens on 12.04.
By "the bug" I mean : receive the e-mail just because you start or resume the
system before 07:30.
Can someone formally mark that the bug also happens on "Precise" and
"Trusty" ?
--
You received this bug notification because you are a m
@Steve (comment #38):
> Under what circumstances are you seeing this problem? Is it a regular
occurrence for you due to something like comment #34 (booting just
before 7:30 every day), or an issue with a previous instance of anacron
being hung?
It's all written in my comment #37.
I had it every
Steve,
Anacron sending out a cryptic e-mail due to a hung cron job is a primary
bug in and of itself. Either don't send out an e-mail at all, or send
an e-mail that doesn't confuse people while leaving them no avenue for
follow-up. You have enough deep knowledge of the system to intuit the
underl
On Tue, Jun 10, 2014 at 02:42:23AM -, Daniel Richard G. wrote:
> If anacron sending out e-mail under such circumstances is a desired
> behavior, could you at least make the message more intelligible, with a
> mention of the likelihood that a previously-started cron job has hung?
> Even nicer w
Steve,
If anacron sending out e-mail under such circumstances is a desired
behavior, could you at least make the message more intelligible, with a
mention of the likelihood that a previously-started cron job has hung?
Even nicer would be some shell magic that greps the process table for
children
gouri,
On Thu, Jun 05, 2014 at 09:02:28AM -, gouri wrote:
> It's June 2014 and this bug still hits the latest LTS release Trusty
> Thar.
Under what circumstances are you seeing this problem? Is it a regular
occurrence for you due to something like comment #34 (booting just
before 7:30 every
It's June 2014 and this bug still hits the latest LTS release Trusty
Thar.
# Why we are here
Some people say "fix the noise" and others say "it's not noise".
What's needed is to fix the noise and keep the signal.
Has anyone used Kevin's patches (see comments #34 and #35) ?
My guess is: many pe
The attachment "Fix only the issue of warnings from cron when anacron is
already running" of this bug report has been identified as being a
patch. The ubuntu-reviewers team has been subscribed to the bug report
so that they can review the patch. In the event that this is in fact
not a patch you c
This patch hits the needs of people having problems with anacron
hanging.
For the issues with hanging, and causing a notification if anacron is
still running long after it should be, I think a separate process is in
order. I could not find any way within upstart to do this, so I wrote a
short scri
It seems like I may be in the minority here, but I am not experiencing
any problems with APT or other things hanging.
My problem is simply that I boot my machine slightly before 7:30 local
time, and anacron is still running as expected when cron tries to start
it. I think the proper way to fix thi
I get these emails from precise machines, most of the times directly after the
installation.
Seems that upstart has trouble sending to dbus and 'start anacron' hangs
forever, see attached strace.
** Attachment added: "strace-start-anacron.txt"
https://bugs.launchpad.net/ubuntu/+source/anacro
Since this can affect automatic security update checks when it strikes,
it is more than just a nuisance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606491
Title:
start: Job is already running: an
** Changed in: anacron (Ubuntu)
Assignee: (unassigned) => Canonical Foundations Team
(canonical-foundations)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606491
Title:
start: Job is already r
** Changed in: anacron (Ubuntu)
Status: Confirmed => Triaged
** Changed in: anacron (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606491
Title:
st
This bug is more serious than I thought. It appears that because of the
aforementioned apt bug (it sometimes never exits when invoked from one
of the cron.daily scripts), anacron has not run any jobs on my system
for the past month.
This is not a good failure mode. It would be much more safe for
Johannes, I agree some of the emails point to an underlying problem that
needs fixing, but some are due to permissible changes, e.g. lengthening
the amount of time after boot before /etc/cron.daily, etc., are kicked
off; see /etc/anacrontab at the end of comment #7. To get a daily
email because o
Daniel: I'm perfectly happy with the situation as it is now. I got an
email notifying me about a problem which eventually pointed me to the
cause of the problem. If we changed anything in the way start or anacron
respond by default to duplicate instances of processes, we may break
other things and
To discard all errors with redirection seems too severe. As I wondered
above, has start's behaviour changed WRT reporting foo is already
running when it's been given --quiet? Perhaps what's needed is a start
option that tells it to consider an already running foo to be OK.
--
You received this
Johannes, --quiet is only applicable to start(8), not to anacron. The
solutions you're proposing are feature requests; please post a separate
bug report for those.
I agree that having some way of being notified about hung jobs would be
nice, but that's beyond the scope of this bug report.
--
You
The description of the --quiet option says: "Reduces output of all
commands to errors only."
Anacron not starting a second instance because another anacron is
already running IS an error, as we expect the start command to
successfully start anacron. We expect anacron to do the periodic jobs
reliab
That's a point, but AFAICS --quiet means that start(8) doesn't print the
"blah start/running" message that it would normally give. Error messages
are unaffected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
I don't see why there is so much discussion about a workaround.
In my view if there is a flag -q or --quiet there should be no need to redirect
output to /dev/null but anacron should really be quiet. Point!
So I think it is a bug if anacron -q exhibits a message about not starting a
second instan
I only ever receive an email if I turn the computer on before 7.30AM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606491
Title:
start: Job is already running: anacron
To manage notifications abou
The logic is already written with the intent of failing silently if
anacron is already running; that's what the "|| :" bit is for. Anacron
can be started from multiple places (various cron entries and pm-utils),
so it has to address the possibility of collisions from two instances
starting at rough
Daniel, I disagree. If you read back through all the bug's comments
you'll see that some of us are getting this email and it has nothing to
do with apt, that's just one instance that can trigger overlapping
anacrons. The solution isn't to discard the error messages. :-)
--
You received this bu
Anacron is hanging only because apt is hanging, however---that's a bug
in the latter, not the former. All anacron is doing wrong is causing the
e-mail to be sent.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
This patch will only cure the symptom (the email being sent), but not
the real problem (anacron hanging). I don't think that's what we want.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606491
Title:
The following change should address this bug:
--- /etc/cron.d/anacron.orig2010-06-20 04:11:29.0 -0400
+++ /etc/cron.d/anacron 2012-01-06 18:03:48.0 -0500
@@ -4,4 +4,4 @@
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
#30 7* * * root test -x /etc/in
In my case, the problem happens because /etc/cron.daily/apt starts apt-
key net-update, which ignores the apt proxy settings.
See https://bugs.launchpad.net/ubuntu/+source/apt/+bug/226780
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
I got this too, and after reading the comments, I think it's both
(ana)cron and apt doing something wrong.
This may also be a security bug, since apt will keep a lock and
automatic updates (which is configured on my system) may not be running
due to a stuck apt process. The apt process is really d
i had this problem for one week now also and found the reason - the apt server
in /etc/apt/sources.list was no longer working and "apt update" hung forever
then.
Just find a new source server and it should work but on the other hand apt
should not block forever which is a bug from "apt" and not
Alden, no, it's nothing to do with an email server as such, although
that may have made it more likely to happen on your system but then an
FTP server or web server may have done so too. My comments #9 and #10
above try to explain why it's happening.
--
You received this bug notification because
I don't have the bug anymore, but I have reinstalled and am now running
Trisquel, which is also Ubuntu based. I think the issue first happened
to me after I installed an email server, which of course you must have I
guess. But I think it could be related to that, although I am far from
an expert. O
Hi everybody,
I'm also affected by this bug.
I confirm in my case that the message is produced by the command found in
/etc/cron.d/anacron :
in this file, there is a rule to start the anacron service everyday at 7:30.
I don't understand what it is for since this service keeps running in
the bac
I get this same error occasionally. I just tried running:
test -x /usr/sbin/anacron || ( cd / && time run-parts -v --report
/etc/cron.daily )
as root.
It terminated with returncode 0 and without any output.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Had this happen again this morning and I checked to see if apt was
stuck. Sure enough:
root 947 0.0 0.0 0 0 ?ZN Apr26 0:00 [apt]
That process can not be killed either, not even with -9.
At least in my case I'm pretty sure this has to do with the automatic
updates.
Got another email this morning. Here's the relevant lines from
/var/log/syslog showing the overlap between the first anacron and the
second started by cron.
Apr 16 07:29:40 orac cron[1097]: (CRON) INFO (pidfile fd = 3)
Apr 16 07:29:40 orac anacron[]: Anacron 2.3 started on 2011-04-1
I think I get this email if I boot within roughly a couple of hours (due
to my longer /etc/anacrontab delays) of 07:30 local time. Perhaps an
anacron from boot time is sleeping for those delays and meanwhile, at
07:30, cron attempts to `start -q anacron', causing noise and the email.
Others could
Just had another occurrence. Again, local time is 07:30:01.
Return-Path: r...@inputplus.co.uk
Delivery-Date: Sat Apr 9 07:30:02 2011
Return-Path:
X-Original-To: root
Delivered-To: r...@inputplus.co.uk
Received: by orac.inputplus.co.uk (Postfix, from userid 0)
I also have automatic security updates turned on.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/606491
Title:
start: Job is already running: anacron
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Been seeing the same problem in Maverick lately. I believe it may have
something to do with automatic upgrades. Do the other people
experiencing this issue have automatic updates turned on?
When manually running apt-get update/upgrade I have seen it hang
indefinitely before possibly due to netwo
I've also just received a similar email from cron.
Return-Path: r...@inputplus.co.uk
Delivery-Date: Tue Mar 29 07:30:01 2011
Return-Path:
X-Original-To: root
Delivered-To: r...@inputplus.co.uk
Received: by orac.inputplus.co.uk (Postfix, from userid 0)
id 2BCF13
Hi click,
that *sleep* you see is from /etc/cron.daily/apt, I think:
# sleep for a random interval of time (default 30min)
# (some code taken from cron-apt, thanks)
random_sleep()
{
# [...]
sleep $TIME
}
EOF
When I get these mails there is an anacron process (ps aux |grep anacron) that
is w
Just to add, tried to collide them manually - no luck
r...@wolfdale:~# test -x /usr/sbin/anacron || ( cd / && time run-parts --report
/etc/cron.daily )
real30m35.078s
user4m44.720s
sys 0m49.480s
r...@wolfdale:~# test -x /usr/sbin/anacron || ( cd / && time run-parts -v
--report /etc/
Just to add some info since original is a very plain. So according my
theory something halts the scripts and the weekly and daily crons match
which explains at least why I`m getting this only on weekly basis.
Output
r...@wolfdale:~# uname -a
Linux wolfdale 2.6.32-24-server #42-Ubuntu SMP Fri Aug 2
52 matches
Mail list logo
