I think it is great support here from you people!
Today I think I might have understood what is happening, and Bill’s
explanations about what might be going on were probably correct in the core,
but not in the details.
Let me try to lay out what I think is going on and where I had my problem
> On Mon, 25 Jul 2022 15:50:15 +, Bill Arlofski said:
>
> On Monday, July 25th, 2022 at 08:54, Martin Simmons =
> wrote:
> >
> > You could try running bacula-fd with debugging output. Unfortunately,
> > it doesn't include timestamps, but you can do it like this:
>
> Hey Martin, Not sure
On Monday, July 25th, 2022 at 08:54, Martin Simmons
wrote:
>
> You could try running bacula-fd with debugging output. Unfortunately,
> it doesn't include timestamps, but you can do it like this:
Hey Martin, Not sure if this is recent or not, but:
8<
$ /opt/comm-bacula/sbin/bacula-fd -?
C
You could try running bacula-fd with debugging output. Unfortunately, it
doesn't include timestamps, but you can do it like this:
bacula-fd -d50,scheduler -f -v ...your normal bacula-fd args... | perl -pe
'use POSIX strftime; print strftime "[%Y-%m-%d %H:%M:%S] ", localtime'
That might show ex
Issue Reported: https://bugs.bacula.org/view.php?id=2657
On Mon, Jul 25, 2022 at 4:37 PM Robert Reihs wrote:
> Hi,
> I have the same problem with a newly bacula 13 installation on debian.
> When modifying the systemctl to startup bacula-sd in foreground the service
> starts fine. When removing i
Hi,
I have the same problem with a newly bacula 13 installation on debian. When
modifying the systemctl to startup bacula-sd in foreground the service
starts fine. When removing it again service is not starting and no error
messages shown. Only output in syslog:
Jul 25 16:21:48 localhost systemd[1
