Hello again, folk,
Checked out there and there's really only a few negligible results
on this problem.
Following a full upgrade, from 2.4.4 to 3.0.2 (all packages), the
bconsole program just won't let me connect.
I've checked both .conf files, passwords/addresses/etc, tried
changing address on both to name, IP, etc. but it won't let me connect.
Output of:
bconsole -c /etc/bacula/bconsole.conf -d 100 -dt
Connecting to Director 10.6.4.238:9101
09-Dec-2009 11:46:56 bconsole: bsock.c:221-0 Current host[ipv4:(ip
address hidden):9101] All host[ipv4:(ip address hidden):9101]
09-Dec-2009 11:46:56 bconsole: bsock.c:155-0 who=Director daemon
host=(ip address hidden) port=9101
(Gets hung here for about 300 seconds or so)
Director authorization problem.
Most likely the passwords do not agree.
If you are using TLS, there may have been a certificate validation error
during the TLS handshake.
Please see
http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION003760000000000000000
for help.
All I see that's noticeable, while debugging bacula-dir, is that the
client tries to connect, and that's about it:
09-Dec-2009 11:46:56 (dir host hidden): bnet.c:670-0 who=client host=(ip
address hidden) port=36131
I'm actually not using TLS or anything, has anyone encountered this
oddity before?
Thanks in advance,
--
Shawn Qureshi
Artemide, Inc.
IT Specialist
<<attachment: artemide-logo.jpg>>
------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
