[Bug 876387] Re: fuser forking uncontrollably in cron job

[Simon Hirscher]

Don't know if it's related but since having tempered with
/etc/cron.d/php5 (see the workaround Graham described) I (as root)
regularly receive the following mail:

Subject: "Cron <root at lvps176-28-19-116> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) (failed)"
Message:
"Unable to run /etc/cron.daily/standard because lockfile /var/lock/cron.daily
acquisition failed. This probably means that the previous day's
instance is still running. Please check and correct if necessary.

lockfile creation failed: cannot create temporary lockfile
run-parts: /etc/cron.daily/standard exited with return code 1"

Taking a look at /var brought:

root at lvps:/home/simon# ls -l /var | grep lock
lrwxrwxrwx  1 root root     9 2011-12-27 22:27 lock -> /run/lock

…whereas /run/lock didn't even exist. So I (re-)created the directory.
Let's whether this fixes it.

Can anyone confirm this?

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/876387

Title:
  fuser forking uncontrollably in cron job

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/876387/+subscriptions