I coincidentally just saw this issue with PostgreSQL over the weekend. In my case, I had updated the postgresql packages (using aptitude) which caused a database shutdown and restart. The bacula director process was brain-damaged and spewed these errors until I recycled it too, after which everything was fine.
Speaking as a lazy SA :-) it would be nice if the director attempted to re-open its database connection when it encounters an error, before punting entirely. In the alternative, I don't think there is any infrastructure to support a forced restart of the director any time the database is cycled, so I guess we'll just have to remember to notice and do this step ourselves, manually. Cheers, Scott [EMAIL PROTECTED]
