Hi Thomas, I have reported this as a bug, and referenced the issue you have experienced as well:
http://bugs.bacula.org/view.php?id=983 Chris Thomas Glatthor wrote: > i have never used this feature, but now i need it. > i can confirm that bacula 2.2.5 (compiled from source on debian 4.0) has the > same problem with postgresql > > > catalog = all, !skipped, !saved > > but i don't know if this is only a configuration problem > (the dird starts fine with that message-resource, but no records are found in > the log-table) > > > looks like a bug-report is needed. > > Best Regards > > Thomas > > Chris Sarginson schrieb: >> Hi Guys, just trying to give this a bump, if it needs a bug report >> submitting then let me know and I will gladly do so - I just need to >> make sure that it's not a stupid config issue that I have messed up. >> >> I have a bacula set up that has been running for a while, and recently I >> introduced an additional backup server to this. >> >> We went with Bacula-mysql 2.2.4 (compared to 2.0.2 on our previous >> servers), added the clients to be backed up, and ran "status all" in >> bconsole. In version 2.0.2 this added all the clients to the "Client" >> MySQL table, and allowed all backups etc to be logged to MySQL. >> Unfortunately in 2.2.4 this is not the case, and nothing was logged to >> MySQL. I have the following line in my bacula-fd.conf for the logging - >> can you let me know if I am missing anything: >> >> catalog = all, !skipped, !saved >> >> I am using the sourceforge provided RPM's of 2.2.4. >> >> Chris >> > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
