Seems the daemon of cronie is not running in willow nor nightshade. Listing the processes with cron name, there's only /usr/sbin/cron which seems to be the daemon for sun crontab.
From clematis process list (where cronie does continue running, so jobs
sent from submit were probably not affected), it seems the daemon which should be running is /opt/ts/sbin/crond.
I've been getting crontab emails less than 5 minutes ago
On Saturday, November 5, 2011, Platonides platonides@gmail.com wrote:
Seems the daemon of cronie is not running in willow nor nightshade. Listing the processes with cron name, there's only /usr/sbin/cron which seems to be the daemon for sun crontab. From clematis process list (where cronie does continue running, so jobs sent from submit were probably not affected), it seems the daemon which should be running is /opt/ts/sbin/crond.
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list:
Yesterday I found my crontab on nightshade empty and I didn't have crontab on willow. I then installed a backup of my crontab on willow (thought there was some issues on nightshade). Now I find my crontab back on nightshade and the crontab installed on willow works as well and caused the jobs run twice.
-Liangent
On Sun, Nov 6, 2011 at 7:55 AM, Platonides platonides@gmail.com wrote:
John wrote:
I've been getting crontab emails less than 5 minutes ago
Sun crontab or cronie? Note that crontab is still running on both.
Toolserver-l mailing list (Toolserver-l@lists.wikimedia.org) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
Hello, At Sunday 06 November 2011 16:54:43 DaB. wrote:
Yesterday I found my crontab on nightshade empty and I didn't have crontab on willow. I then installed a backup of my crontab on willow (thought there was some issues on nightshade). Now I find my crontab back on nightshade and the crontab installed on willow works as well and caused the jobs run twice.
I killed the cron-daemon 2 days ago by accident and started it again yesterday after Platonides eMail (see [1]). I'm sorry that it caused some trouble.
BTW: If you use cronsub, you can also use the submit-server, that have a redundant cronie (see [2]).
Sincerly, DaB.
[1] https://jira.toolserver.org/browse/MNT-1129 [2] https://wiki.toolserver.org/view/Job_scheduling#submit.toolserver.org
-Liangent
On Sun, Nov 6, 2011 at 11:58 PM, DaB. WP@daniel.baur4.info wrote:
Hello, At Sunday 06 November 2011 16:54:43 DaB. wrote:
Yesterday I found my crontab on nightshade empty and I didn't have crontab on willow. I then installed a backup of my crontab on willow (thought there was some issues on nightshade). Now I find my crontab back on nightshade and the crontab installed on willow works as well and caused the jobs run twice.
I killed the cron-daemon 2 days ago by accident and started it again yesterday after Platonides eMail (see [1]). I'm sorry that it caused some trouble.
BTW: If you use cronsub, you can also use the submit-server, that have a redundant cronie (see [2]).
Sincerly, DaB.
[1] https://jira.toolserver.org/browse/MNT-1129 [2] https://wiki.toolserver.org/view/Job_scheduling#submit.toolserver.org
-Liangent
-- Userpage: [[:w:de:User:DaB.]] — PGP: 2B255885
Now I find my cronjobs still run twice a time even if I clear my crontab on nightshade. Can someone have a look and tell me what's wrong?
-Liangent
On 09/11/11 09:06, Liangent wrote:
Now I find my cronjobs still run twice a time even if I clear my crontab on nightshade. Can someone have a look and tell me what's wrong?
-Liangent
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.
Does something really need sun crontab? Otherwise, I propose to make cronie (which seems to be the most advanced) take over sun crontab.
On Thu, Nov 10, 2011 at 12:47 AM, Platonides platonides@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
On Thu, Nov 10, 2011 at 18:08, Liangent wrote:
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
Yes, that makes things even more complex. You may like this alias I have in my .bashrc: alias crontab=cronie
toolserver-l@lists.wikimedia.org