This may be more of a question for the users group but I may be
experiencing some difficulty with getting the moderators to approve my
postings there and this is also a question for the developers...
I have a file daemon that keeps dying on me, after it has been running
for awhile, for some unknown reason, and I would like to track down why
it is failing. Nothing appears in the system log files. A common
requirement for good robust software it to have the code well
instrumented so that the user can turn on logging to find out why a
failure may be occurring. Is the file and storage daemon's code
instrumented?
I did try starting the file daemon with the following command -
/usr/sbin/bacula-fd -v -T -d 10 -dt -c /etc/bacula/bacula-fd.conf
but that has not produced any output that I can find when running as a
systemd service. I looked in the working directory at /usr/share/bacula
but found nothing there either. (if I run it standalone in the
foreground I do get one line of output on the console terminal but that
is not going to be helpful for tracking down why it is failing when
running as a daemon process.) Where is this "trace" file located on
Linux systems that the -T option is suppose to be creating? Is that
location something that is user configurable? (it should be) I checked
the system log files, and nada.
I guess my bottom line question is, how does one turn on logging for the
file and storage daemons, I would expect it to be somewhat similar to
the way logging the director daemon is turned on, but I don't find any
documentation on how...
Marc..
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
