Thanks for the report. If you haven't restarted the Pulse master since the database went down I would suggest giving that a try: sometimes Pulse will not recover well itself from a long database outage. If that doesn't work then often in a case like this there will be some clues in the master logs (under $PULSE_HOME/logs). It sounds like an exception is being thrown when trying to load the data, and that should be recorded in one of the pulse*.log files. If you can find a stack trace to report (via here, or even by sending the logs to firstname.lastname@example.org
) that should help get to the bottom of things.