bin/zeoraid: Exception when trying to connect to nonexistent server
Bug #463763 reported by
ChrisW
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| gocept.zeoraid |
Fix Released
|
Undecided
|
Christian Theune | ||
Bug Description
I have no zeoraid server running on the default 127.0.0.1:8100
When I do:
$ bin/zeoraid status
...I'd expect an error about not being able to connect. What I actually get is:
Traceback (most recent call last):
File "bin/zeoraid", line 25, in <module>
gocept.
File "/home/
command(
File "/home/
print self.raid.
AttributeError: 'ClientStorage' object has no attribute 'raid_status'
Revision history for this message
| ChrisW (chris-simplistix) wrote | #1 |
| summary: |
- Exception when trying to connect to nonexistent server + bin/zeoraid: Exception when trying to connect to nonexistent server |
Revision history for this message
| Christian Theune (ctheune) wrote | #2 |
| Changed in gocept.zeoraid: | |
| status: | New → Fix Committed |
| Changed in gocept.zeoraid: | |
| assignee: | nobody → Christian Theune (ct-gocept) |
| status: | Fix Committed → Fix Released |
Revision history for this message
| ChrisW (chris-simplistix) wrote | #3 |
To post a comment you must log in.
Hmm, I've been running buildouts a lot this morning, but I'm still using the gocept.
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?