collection-monitor should not crash when it cannot connect to the collection-server

Bug #507253 reported by Chris Wagner
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Resonate
Fix Committed
Medium
Unassigned

Bug Description

Rather than crash/close, collection-monitor should just continue in its usual loop of sleeping and then rescanning, so all will continue as normal once the collection-server is back up.

Here's the error that gets logged, at present, when the collection-monitor stumbles across this problem:
  collection-monitor shutting down because of error: getAddrInfo: does not exist (Temporary failure in name resolution)

Changed in resonate:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Chris Wagner (chris-wagner) wrote :

Fixed in revision 769.

Changed in resonate:
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.