search

legastero / Kestrel

Kestrel is a job scheduler and dispatcher for distributed computing systems, particularly Virtual Organization Clusters, and uses XMPP for monitoring the state of all compute elements in the cluster and dispatching tasks.
github.com/legastero/Kestrel
Apache License 2.0
31 stars 7 forks source link

Kestrel Status some times throws an error #2

Open h4ck3rm1k3 opened 13 years ago

h4ck3rm1k3 commented 13 years ago

First it does not work mdupont@space-station:~/experiments/osm/dist/SleekXMPP$ kestrel status 2011-06-12 09:51:04,311 INFO Negotiating TLS 2011-06-12 09:51:04,311 INFO Using SSL version: 3 2011-06-12 09:51:04,437 INFO Node set to: h4ck3rm1k3@h4ck3rm1k3-sixxs.mooo.com/4ed4e7c6 2011-06-12 09:51:04,511 INFO Online Workers: 2 2011-06-12 09:51:04,512 INFO Available Workers: 2 2011-06-12 09:51:04,512 INFO Busy Workers: 0 Exception in thread sheduler_process (most likely raised during interpreter shutdown): Traceback (most recent call last): File "/usr/lib/python2.6/threading.py", line 532, in __bootstrap_inner File "/usr/local/lib/python2.6/dist-packages/sleekxmpp/xmlstream/xmlstream.py", line 1093, in run_with_except_hook <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute 'excepthook'

then it works: mdupont@space-station:~/experiments/osm/dist/SleekXMPP$ kestrel status 2011-06-12 09:51:08,812 INFO Negotiating TLS 2011-06-12 09:51:08,812 INFO Using SSL version: 3 2011-06-12 09:51:08,983 INFO Node set to: h4ck3rm1k3@h4ck3rm1k3-sixxs.mooo.com/3d1ff001 2011-06-12 09:51:09,159 INFO Online Workers: 2 2011-06-12 09:51:09,159 INFO Available Workers: 2 2011-06-12 09:51:09,159 INFO Busy Workers: 0

Then I get a different error : mdupont@space-station:~/experiments/osm/dist/SleekXMPP$ kestrel status 2011-06-12 09:52:43,771 INFO Negotiating TLS 2011-06-12 09:52:43,771 INFO Using SSL version: 3 2011-06-12 09:52:43,940 INFO Node set to: h4ck3rm1k3@h4ck3rm1k3-sixxs.mooo.com/959873be 2011-06-12 09:52:44,065 INFO Online Workers: 2 2011-06-12 09:52:44,065 INFO Available Workers: 2 2011-06-12 09:52:44,065 INFO Busy Workers: 0 Exception in thread stream_event_handler_0 (most likely raised during interpreter shutdown):Exception in thread sheduler_process (most likely raised during interpreter shutdown):

then it works again : mdupont@space-station:~/experiments/osm/dist/SleekXMPP$ kestrel status 2011-06-12 09:53:02,072 INFO Negotiating TLS 2011-06-12 09:53:02,073 INFO Using SSL version: 3 2011-06-12 09:53:02,247 INFO Node set to: h4ck3rm1k3@h4ck3rm1k3-sixxs.mooo.com/b4a098ca 2011-06-12 09:53:02,423 INFO Online Workers: 2 2011-06-12 09:53:02,423 INFO Available Workers: 2 2011-06-12 09:53:02,423 INFO Busy Workers: 0

legastero commented 13 years ago

The errors are sometimes raised during the shutdown process as daemon threads in SleekXMPP are terminated in arbitrary order and references are destroyed.