-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Really, this is not a case that you'd see all that often to begin with. Generally you'll see an error where *Console* is instead a job name. Since most of my job names only run on one FD, it's obvious which it's talking about. What is it you were trying to do in the first place when you got this error? I'm guessing console commands in a cron job.
I agree that this information should be in the error message, but it's also possible for you to add it in. Witness earlier patches mailed to this list to print the post-job stats in a more human-readable form. I am not a coder, or I'd take it on myself. Incidentally, I changed the subject because it was rude and condescending. Calling someone else's work USELESS is obnoxious. Error messages are insufficient or something with any tact would be appreciated in the future. =R Jo Rhett wrote: > On Aug 1, 2006, at 5:48 PM, Kern Sibbald wrote: >> long. Generally one knows exactly which daemon you are dealing with >> from the >> context unless you are driving the console with a script. > > These messages were e-mailed to me. No other context is provided. > Message settings at default / standard from the example configuration > files. > >>> On Jul 28, 2006, at 10:01 AM, Jo Rhett wrote: >>>> I haven't the foggiest idea which File Daemons it was unable to >>>> communicate with. Can we please expand the error message to include >>>> this information? >>>> >>>> Begin forwarded message: >>>>> From: (Bacula) [EMAIL PROTECTED] >>>>> Date: July 25, 2006 2:37:01 PM PDT >>>>> To: [EMAIL PROTECTED] >>>>> Subject: Bacula daemon message >>>>> >>>>> 25-Jul 14:21 backup0-dir: *Console*.2006-07-25_14.21.47 Fatal >>>>> error: Unable to authenticate with File daemon. Possible causes: >>>>> Passwords or names not the same or >>>>> Maximum Concurrent Jobs exceeded on the FD or >>>>> FD networking messed up (restart daemon). >>>>> Please see http://www.bacula.org/rel-manual/ >>>>> faq.html#AuthorizationErrors for help. >>>>> 25-Jul 14:22 backup0-dir: *Console*.2006-07-25_14.21.47 Fatal >>>>> error: Unable to authenticate with File daemon. Possible causes: >>>>> Passwords or names not the same or >>>>> Maximum Concurrent Jobs exceeded on the FD or >>>>> FD networking messed up (restart daemon). >>>>> Please see http://www.bacula.org/rel-manual/ >>>>> faq.html#AuthorizationErrors for help. > - -- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE0PbVmb+gadEcsb4RAoTHAJ9UekvQzwFDQ6F6vHTvRGGh/luEdQCeOles XkpyoBkdB7+e33BvjRkq+IE= =w6LA -----END PGP SIGNATURE----- ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
