Hello, There are no moderators for any of the email accounts. If you are not subscribed your messages will be discarded as documented on the web site. If you are subscribed they are delivered to the email list.
Concerning logging. Bacula "logging" is done through the Messages resource, so what is "logged" depends on how you configure the Director and the individual clients. You may get a better idea about logging by looking at the current default bacula-xx.conf files and consulting the Messages resource documentation in the manual. By the way, your problem seems to be a support issue, so you would probably get better help on the bacula-users email list. Best regards, Kern PS: I am not sure that turning tracing on (-T) is a good idea and setting such a low debug level is a good idea unless you are capturing the STDOUT and only in a test or debug setting. systemd probably throws away STDOUT output by default, which is rather standard for a daemon. On 5/12/19 5:04 AM, Gary R. Schmidt wrote: > On 12/05/2019 02:06, Marc Chamberlin via Bacula-devel wrote: >> 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... >> > Whenever I see "logging problems" and "systemd" in the same message, I > presume that the fault lies with systemd, always. It saves time. > > Up the level of debugging, 100 is the usual sensible level, and run > again in the foreground, and see if that helps. > > Oh, did you build it yourself or use some pre-compiled version - if > so, bug whoever created it if it wasn't downloaded from the Bacula site. > > Cheers, > Gary B-) > > > _______________________________________________ > Bacula-devel mailing list > Bacula-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-devel > _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
