The Xron Dispatcher always makes a log entry (or tries to) when it finds a ready event in the Schedule catalog and tries to fire it. If there are no log entries when you expect them, I can think of the following possible explanations: 1. There is a catalog bug. Some bugs were introduced and fixed in recent Zope releases. Make sure you have all the patches. 2. The method was removed from the catalog due to an error during an earlier trigger. This should leave an earlier entry in the log. 3. The method was not rescheduled after the last firing. This would probably be due to application logic. I hope that will give you a good idea of where to look for the problem. Xron DTML Methods that are not in the Schedule can usually be restarted without restarting Zope. Just pretend to do an edit operation by clicking on the Change button on the manage_edit panel. That will cause recataloging in the Schedule. You may or may not have to change the scheduling parameters first. I would avoid scheduling a lot of events for the same time. It shouldn't cause any problems, but you never know. Xron will serialize them anyway. What platform are you running on? I've found on my NT4 platform that occasionally Client.py gets a socket error (for reasons I haven't discovered yet), causing the trigger process to fault and resulting in removal of the method from the Schedule. You might see some tracks with the Event Viewer -- but I don't know much about that. -- HTH -- Loren

-----Original Message----- From: zope-admin@zope.org [mailto:zope-admin@zope.org]On Behalf Of Capesius, Alan Sent: Thursday, May 03, 2001 14:25 To: zope@zope.org Subject: [Zope] Xron not firing reliably

I'm using a sendmail operation in three identical xron methods. The events are scheduled for 12:00:00 each day. They can be triggered manually or scheduled for other times, but they do not fire reliably over time. That is, they will work the first and maybe second time but will not fire repeatedly over several days. No output goes to the STUPID_LOG_FILE when this happens.

Restarting the Zope service will activate the unfired events and log them.

Anyone have any ideas on what might be going on or not going on here?

I'm currently running a test with a simple test logging event that fires every minute to see if it will eventually break down.

Thanks,

Alan Capesius, MCSE/NTCIP+20 Technical Support Engineer Sysmex Corporation of America capesiusa@sysmex.com

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )