Hello, On 5/2/2007 9:09 PM, Darien Hager wrote: > I don't seem to have any .trace files from using setdebug.
Which versions? I did create trace files using 'setdebug level= trace=1 client/sd/dir' commands on unix, FreeBSD, Solaris and Windows, so I think it's safe to say it does work :-) > Am I doing > something wrong, misreading the documentation, etc? > > Running the command, everything appears okay... >> *setdebug >> Enter new debug level: 200 >> Available daemons are: >> 1: Director >> 2: Storage >> 3: Client >> 4: All >> Select daemon type to set debug level (1-4): 4 >> Connecting to Storage daemon mysd at storageserver.example.com:9103 >> 3000 OK setdebug=200 >> Connecting to Client one.example.com at one.example.com:9102 >> 2000 OK setdebug=200 >> Connecting to Client two.example.com at two.example.com:9102 >> 2000 OK setdebug=200 >> Connecting to Client three.example.com at three.example.com:9102 >> 2000 OK setdebug=200 > [etc.] > > I also tried "setdebug level=200 trace=1 all" to the same effect. > > When I tried operations I know create log messages at that level, such > as jobs and status requests, no bacula.trace files are created. If I > create the files, nothing is appended to them. I've checked this on the > Director and the File Daemons. I'm using /proc/ to find their current > working directories where the documentation says trace files will be made. you could even use lsof to see which files the daemons access :-) Personally, I prefer simply looking into the configured working drectory :-) > bacula/[EMAIL PROTECTED] /var/bacula # rm *.trace > bacula/[EMAIL PROTECTED] /var/bacula # ls *.trace > ls: *.trace: No such file or directory Now: > #setdebug level=200 trace=1 sd=DLT > Connecting to Storage daemon DLT at goblin:9103 > 3000 OK setdebug=200 And: > bacula/[EMAIL PROTECTED] /var/bacula # ls -lh *.trace > -rw-r----- 1 root root 100 May 2 22:25 goblin-sd.trace >> If trace=1 is set, then tracing will be enabled, and the daemon will >> be placed in trace mode, which means that all debug output as set by >> the debug level will be directed to the file bacula.trace in the >> current directory of the daemon. Normally, tracing is needed only for >> Win32 clients where the debug output cannot be written to a terminal >> or redirected to a file. When tracing, each debug output message is >> appended to the trace file. You must explicitly delete the file when >> you are done. > > Any ideas on why I'm not getting the debug data? Looking into the wrong directories? Try using lsof, for example. With tracing enabled: > bacula/[EMAIL PROTECTED] /var/bacula # lsof -c bacula-sd | grep trace > bacula-sd 653 root 21u REG 8,7 825 42882 > /var/bacula/goblin-sd.trace > bacula-sd 657 root 21u REG 8,7 825 42882 > /var/bacula/goblin-sd.trace > bacula-sd 659 root 21u REG 8,7 825 42882 > /var/bacula/goblin-sd.trace > bacula-sd 12267 root 21u REG 8,7 825 42882 > /var/bacula/goblin-sd.trace > bacula-sd 12271 root 21u REG 8,7 825 42882 > /var/bacula/goblin-sd.trace > bacula-sd 12279 root 21u REG 8,7 825 42882 > /var/bacula/goblin-sd.trace > bacula-sd 18459 root 21u REG 8,7 825 42882 > /var/bacula/goblin-sd.trace > bacula-sd 23077 root 21u REG 8,7 825 42882 > /var/bacula/goblin-sd.trace > bacula-sd 23081 root 21u REG 8,7 825 42882 > /var/bacula/goblin-sd.trace After I turned tracing off: > bacula/[EMAIL PROTECTED] /var/bacula # lsof -c bacula-sd | grep trace > bacula/[EMAIL PROTECTED] /var/bacula # So, I'd bet that tracing does work. Arno -- IT-Service Lehmann [EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
