Hello Ana,

 > Have you checked DNS? Which is the output for dig tux64.home.lan? It 
 > seems
 > you have a second loopback interface defined in your system and bacula
 > daemons are using this interface for listening to connections.

indeed, I've check my DNS settings and fixed/added it for my test 
machine. Now the IPs are OK:

$ sudo netstat -nltup | grep bacula
tcp        0      0 192.168.1.11:9101       0.0.0.0:* 
LISTEN      7933/bacula-dir
tcp        0      0 192.168.1.11:9102       0.0.0.0:* 
LISTEN      8195/bacula-fd
tcp        0      0 192.168.1.11:9103       0.0.0.0:* 
LISTEN      7792/bacula-sd

from bat I've got now:
$ sudo bat -d100
bat: bsock.c:208-0 Current [fe80::21f:d0ff:fe9d:e781]:9101 All 
[fe80::21f:d0ff:fe9d:e781]:9101 192.168.1.11:65535
bat: bsock.c:208-0 Current 192.168.1.11:9101 All 
[fe80::21f:d0ff:fe9d:e781]:9101 192.168.1.11:9101
bat: bsock.c:137-0 who=Director daemon host=tux64.home.lan port=9101
bat: bsock.c:310-0 OK connected to server  Director daemon 
tux64.home.lan:9101.
bat: cram-md5.c:119-0 cram-get received: auth cram-md5 
<2091799515.1433789819@bacula-tux64-dir> ssl=0
bat: cram-md5.c:139-0 sending resp to challenge: TANvGgZM7EZAZx+F24xoOB
bat: cram-md5.c:67-0 send: auth cram-md5 challenge 
<936881031.1433789819@bat> ssl=0
bat: cram-md5.c:86-0 Authenticate OK M1gBO9/nV4sH4kQc2m+ZgB
bat: bcomm/dircomm_auth.cpp:142-0 >dird: 1000 OK auth
bat: bcomm/dircomm_auth.cpp:152-0 <dird: 1000 OK: 1 bacula-tux64-dir 
Version: 7.0.5 (28 July 2014)

but the tool doesn't show any contents.

$ bacula-tray-monitor -d100 -c /etc/bacula/tray-monitor.conf 

tray-monitor: bsock.c:208-0 Current [fe80::21f:d0ff:fe9d:e781]:9101 All 
[fe80::21f:d0ff:fe9d:e781]:9101 192.168.1.11:65535
tray-monitor: bsock.c:208-0 Current 192.168.1.11:9101 All 
[fe80::21f:d0ff:fe9d:e781]:9101 192.168.1.11:9101
tray-monitor: bsock.c:137-0 who=Director daemon host=tux64.home.lan 
port=9101
tray-monitor: bsock.c:310-0 OK connected to server  Director daemon 
tux64.home.lan:9101.
tray-monitor: cram-md5.c:119-0 cram-get received: auth cram-md5 
<1072279248.1433790129@bacula-tux64-dir> ssl=0
tray-monitor: cram-md5.c:139-0 sending resp to challenge: 
z5+7IV+r3W/Z+F+Ky6+YaA
tray-monitor: cram-md5.c:67-0 send: auth cram-md5 challenge 
<416437936.1433790129@tray-monitor> ssl=0
tray-monitor: cram-md5.c:86-0 Authenticate OK CW9Ft9IaG6Q3J/Zytzco3B
tray-monitor: authenticate.cpp:81-0 >dird: 1000 OK auth
tray-monitor: authenticate.cpp:88-0 <dird: 1000 OK: 1 bacula-tux64-dir 
Version: 7.0.5 (28 July 2014)
tray-monitor: bsock.c:208-0 Current [fe80::21f:d0ff:fe9d:e781]:9102 All 
[fe80::21f:d0ff:fe9d:e781]:9102 192.168.1.11:65535
tray-monitor: bsock.c:208-0 Current 192.168.1.11:9102 All 
[fe80::21f:d0ff:fe9d:e781]:9102 192.168.1.11:9102
tray-monitor: bsock.c:137-0 who=File daemon host=tux64.home.lan port=9102
tray-monitor: bsock.c:310-0 OK connected to server  File daemon 
tux64.home.lan:9102.
tray-monitor: cram-md5.c:119-0 cram-get received: auth cram-md5 
<284699536.1433790129@bacula-tux64-fd> ssl=0
tray-monitor: cram-md5.c:139-0 sending resp to challenge: 
Ti/BYB+Du5/jjU+1Z8/+mD
tray-monitor: cram-md5.c:67-0 send: auth cram-md5 challenge 
<1345356675.1433790129@tray-monitor> ssl=0
tray-monitor: cram-md5.c:86-0 Authenticate OK S6/bG4+UfW/oDE+ePRYYsD
tray-monitor: bsock.c:208-0 Current [fe80::21f:d0ff:fe9d:e781]:9103 All 
[fe80::21f:d0ff:fe9d:e781]:9103 192.168.1.11:65535
tray-monitor: bsock.c:208-0 Current 192.168.1.11:9103 All 
[fe80::21f:d0ff:fe9d:e781]:9103 192.168.1.11:9103
tray-monitor: bsock.c:137-0 who=Storage daemon host=tux64.home.lan port=9103
tray-monitor: bsock.c:310-0 OK connected to server  Storage daemon 
tux64.home.lan:9103.
tray-monitor: cram-md5.c:119-0 cram-get received: authenticate.c:86 Bad 
Hello command from Director at client: Hello Director bacula-tux64-mon 
calling

tray-monitor: cram-md5.c:124-0 Cannot scan received response to 
challenge: authenticate.c:86 Bad Hello command from Director at client: 
Hello Director bacula-tux64-mon calling

08-Jun 21:02 tray-monitor JobId 0: Fatal error: authenticate.cpp:126 
Director and Storage daemon passwords or names not the same.
Please see 
http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION00260000000000000000
 
for help.

I didn't start any jobs until now - I have to dive into bconsole, which 
seems to connect without problems so far (list jobs did show my old jobs 
from prior installation).

Thank you,
Olaf

------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users