On Thu, Nov 10, 2011 at 12:47 AM, Platonides <platonides(a)gmail.com> wrote:
I suspect you had your crons in nightshade inside
cronie and the events
looked like this:
* cronie daemon stopped working.
* You did crontab -l (looked at sun crontab) and thought it was empty
* You installed it inside willow crontab
* cronie daemon is restarted
* Your crons are run both from nightshade cronie and crontab
* You cleared your crontab with crontab -r, but as it is using cronie
(you would have needed cronie -r), nothing changed.
* Your crons are still run from both servers.
After some check I thought the fact was:
* I install my crontab on nightshade crontab (when it was still running Linux)
* nightshade is re-installed as Solaris and my crontab gets lost
* River publishes a notice and askes us to type 'cronie
crontab.before_nightshade_reinstall'
* I do it on willow but forget these things and think everything is
still the same as what it was before nightshade-reinstall
* cronie daemon stops working
* I run crontab -e on nightshade (I remembered incorrectly that I'm
using crontab on nightshade)
* I find my crontab empty and think there's something wrong on nightshade
* I install crontab.before_nightshade_reinstall on willow crontab
* at the same time DaB. publishes the notice that he stopped cronie
and restarted it
* I don't remember the existence of cronie and think he's talking about crontab
* Now my jobs run twice. I think one runs on willow and another on nightshade
* I check my crontab on willow and nightshade and make sure only one exists.
* I still find my jobs run twice so I send the mail.
-Liangent