Public bug reported:

I've been checking some apparently random dep8 failures in munin that
are annoying, and I think I have identified one class of errors.

The failure is that /var/cache/munin/www/ isn't empty, but the test
cleans it like this:

# set up clean env for testing the scripts
service cron stop
rm -rf /var/cache/munin/www/*

Whenever the munin-cron test fails, I noticed it's close to the */5 cron
mark. I suspect a cron job might be running already when cron is
stopped.

Here are some samples of when this test failed:
autopkgtest [06:05:05]: test master-cron: [-----------------------
autopkgtest [15:25:08]: test master-cron: [-----------------------
autopkgtest [17:00:10]: test master-cron: [-----------------------

When it passed:
autopkgtest [16:31:56]: test master-cron: [-----------------------
autopkgtest [20:23:58]: test master-cron: [-----------------------
autopkgtest [14:25:54]: test master-cron: [-----------------------

But there are also outliers for when it passed:
autopkgtest [00:02:07]: test master-cron: [-----------------------
autopkgtest [09:44:10]: test master-cron: [-----------------------

It's probably worth it to enhance this test by also killing some munin scripts. 
The cron.d file specifies:
*/5 * * * *     munin if [ -x /usr/bin/munin-cron ]; then /usr/bin/munin-cron; 
fi

munin-cron runs:
munin-update
munin-limits
munin-html
munin-graph

I suggest a killall for these processes right after stopping the cron
service, and before the rm -rf /var/cache/munin/www/* and starting the
tests.

** Affects: munin (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: dep8 update-excuse

** Tags added: update-excuse

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865938

Title:
  DEP8: master-cron can fail if started close to */5

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

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to