Re: [Bacula-users] Could not connect to server Director daemon ....
2015-06-09 13:22:30
Am 08.06.2015 um 21:15 schrieb olx69:
> 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).
after restart, I got:
$ sudo netstat -nltup | grep bacula
tcp 0 0 127.0.0.2:9101 0.0.0.0:* LISTEN
855/bacula-dir
tcp 0 0 127.0.0.2:9102 0.0.0.0:*
LISTEN 857/bacula-fd
tcp 0 0 127.0.0.2:9103 0.0.0.0:*
LISTEN 851/bacula-sd
after restarting the bacula services netstat got the right IP to listen
to. Strange ....
Anyway, parts of the backup starts, expect the Job to backup the
catalog: From mail:
09-Jun 18:45 bacula-tux64-dir JobId 304: shell command: run BeforeJob
"/usr/libexec/bacula/make_catalog_backup.pl MyCatalog"
09-Jun 18:45 bacula-tux64-dir JobId 304: BeforeJob: Can't find your
catalog (MyCatalog) in director configuration
09-Jun 18:45 bacula-tux64-dir JobId 304: Error: Runscript: BeforeJob
returned non-zero status=1. ERR=Child exited with code 1
09-Jun 18:45 bacula-tux64-dir JobId 304: Error: Bacula bacula-tux64-dir
7.0.5 (28Jul14):
Build OS: x86_64-redhat-linux-gnu redhat Two)
JobId: 304
Job: BackupCatalog.2015-06-09_18.35.00_05
Backup Level: Full
Client: "bacula-tux64-fd" 7.0.5 (28Jul14)
x86_64-redhat-linux-gnu,redhat,Two)
FileSet: "Catalog" 2015-02-16 16:01:47
Pool: "Default" (From Job resource)
Catalog: "MyCatalog" (From Client resource)
Storage: "File" (From Job resource)
Scheduled time: 09-Jun-2015 18:35:00
Start time: 09-Jun-2015 18:45:25
End time: 09-Jun-2015 18:45:25
Elapsed time: 0 secs
Priority: 11
FD Files Written: 0
SD Files Written: 0
FD Bytes Written: 0 (0 B)
SD Bytes Written: 0 (0 B)
Rate: 0.0 KB/s
Software Compression: None
VSS: no
Encryption: no
Accurate: no
Volume name(s):
Volume Session Id: 0
Volume Session Time: 0
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 1
SD Errors: 0
FD termination status:
SD termination status:
Termination: *** Backup Error ***
but: /etc/bacula/bacula-dir.conf
...
@/etc/bacula/bacula-dir.conf.d/catalogs.conf
with:
Catalog {
Name = MyCatalog
dbname = "bacula"
dbuser = "bacula"
dbpassword = ""
}
Strange, thanks
Olaf
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Bacula-users] Could not connect to server Director daemon ...., olx69
- Re: [Bacula-users] Could not connect to server Director daemon ...., Ana Emília M. Arruda
- Re: [Bacula-users] Could not connect to server Director daemon ...., olx69
- Message not available
- Re: [Bacula-users] Could not connect to server Director daemon ...., olx69
- Re: [Bacula-users] Could not connect to server Director daemon ....,
olx69 <=
- Re: [Bacula-users] Could not connect to server Director daemon ...., Ana Emília M. Arruda
- Re: [Bacula-users] Could not connect to server Director daemon ...., olx69
- Re: [Bacula-users] Could not connect to server Director daemon ...., Ana Emília M. Arruda
- Re: [Bacula-users] Could not connect to server Director daemon ...., olx69
- Re: [Bacula-users] Could not connect to server Director daemon ...., Ana Emília M. Arruda
- Re: [Bacula-users] Could not connect to server Director daemon ...., olx69
- Re: [Bacula-users] Could not connect to server Director daemon ...., olx69
- Re: [Bacula-users] Could not connect to server Director daemon ...., Ana Emília M. Arruda
- Re: [Bacula-users] Could not connect to server Director daemon ...., olx69
- Re: [Bacula-users] Could not connect to server Director daemon ...., Ana Emília M. Arruda
|
|
|