, the installer only creates a bconsole.exe, no other *.exe.
No bacula-fd or bacula-sd...
Is this expected behaviour or may it have something to do with my
windows root isn't c:\ ( actually f:\ in this case )?
--
Andreas Aronsson
Mobil: +46 704 566 595
www.aron.nu
"I'd rather have fr
list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Andreas Aronsson
Mobil: +46 704 566 595
www.aron.nu
"I'd rather have friends who care than friends who agree with me."
- Arlo Guthrie
t these changes to the manual to someone perhaps?
rgds
Andreas Aronsson wrote:
Remind me again, what you're doing and the symptoms? I'm not
convinced it's the Director.
I am connecting through bconsole, issuing the command 'run' and
selecting the only job I've s
09:02 x-dir: x.2006-03-09_09.02.34 Fatal error:
Authorization problem: Remote server requires TLS.
My conclusion is thus
bconsole -> [issuing command] -> director -> [tries to connect] ->
filedaemon [who demands TLS handshake] -> director fails and stops
Perhaps I am wrong
Dan Langille wrote:
and bacula-fd.conf:
# List Directors who are permitted to contact this File
daemon
#
;
Director {
Name = x-dir
.
TLS Require = yes
TLS Verify Peer = no
shouldn't this be yes? It is for me.
Changed to yes, same result...
ors to verify the authenticity of this file
daemon
TLS Certificate = /etc/ssl/x/cert.pem
TLS Key = /etc/ssl/x/key.pem
SO the director should be able to TLS, and the fd should let the
director in, no?
Dan Langille wrote:
On 8 Mar 2006 at 15:30, Andreas
his.example.cxx/[EMAIL PROTECTED],
ERR=18:self signed certificate
08-Mar 15:26 bconsole: ERROR in tls.c:83 Connect failure:
ERR=error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate
verify failed
--
Andreas Aronsson
Mobil: +46 704 566 595
www.aron.nu
"I'd rather have
