Hi,
I had "TLS Verify" Peer disabled in bacula-dir.conf so why to define
allowed CN's?
Nevertheless, I added TLS Allowed CN, switched to TLS Verify = yes and
also added the TLS Certificate / TLS Key in bconsole.conf (don't think
that they are mandatory either).
However, the behavior is exactly the
> Hello Heitor,
> root@bacula-dir:/etc/bacula# bacula-dir -t
> root@bacula-dir:/etc/bacula# echo $?
> 0
>
> There seems to be no syntax error in configuration because after
> restart everything is ok again. After reloading, I get the following
> messages:
>
> 22-Dec 13:02 bacula-dir.grnet.gr-dir
Hello Heitor,
root@bacula-dir:/etc/bacula# bacula-dir -t
root@bacula-dir:/etc/bacula# echo $?
0
There seems to be no syntax error in configuration because after
restart everything is ok again. After reloading, I get the following
messages:
22-Dec 13:02 bacula-dir.grnet.gr-dir JobId 0: Fatal error
>>> Hello,
>>> we are on Linux Debian Wheezy and we use version bacula-director-mysql
>>> 5.2.6+dfsg-9. We experience a faulty communication between bconsole
>>> and director daemon after reloading bacula-dir. Specifically, when
>>> everything is ok and without TLS configuration we get the followi
Hi Ana,
exactly. After restarting the daemon, bconsole is connected
sucessfully until the next reload
Regards,
Kostis
On 22 December 2015 at 11:30, Ana Emília M. Arruda
wrote:
> Hello Kostis,
>
> When you say "If we restart bacula-dir service, everything is ok again", you
> mean that bacula-dir
Hello Kostis,
When you say "If we restart bacula-dir service, everything is ok again",
you mean that bacula-dir service is running and you successfully enter
bconsole with SSL/TLS configured?
Best regards,
Ana
On Tue, Dec 22, 2015 at 10:05 AM, Kostis Fardelas
wrote:
> Hello,
> we are on Linux
Hello,
we are on Linux Debian Wheezy and we use version bacula-director-mysql
5.2.6+dfsg-9. We experience a faulty communication between bconsole
and director daemon after reloading bacula-dir. Specifically, when
everything is ok and without TLS configuration we get the following:
{code}
*root@bacu
