gocept.zeoraid

  1. Bug #463763
  2. Comment #1

Comment 1 for bug 463763

Revision history for this message
ChrisW (chris-simplistix) wrote :

Hmm, I've been running buildouts a lot this morning, but I'm still using the gocept.zeoraid-1.0b3-py2.6.egg and yet the behaviour has changed :-(

I no longer get the exception, however, for bin/zeoraid [status|details], if the server is not there, I get:

(8254) CW: error connecting to ('127.0.0.1', 8100): ECONNREFUSED

over and over. This is bad if you want to use bin/zeoraid status for automated monitoring, where you want it to try once and return an error code if the server is not there. Do you guys know how this could be fixed?