Re: [Bacula-users] Could not connect to server Director daemon ....
Hello Ana,
Have you checked if this address/port (tux64.home.lan:9101) is not being
used by another process? Your original bacula-dir.conf (the last post)
was configured to use locahost and not tux64.home.lan as your are trying
now.
this comes up from time to time - I see only one mail every two? days,
bacula it self (regardless the problem with the traymon) works. Anyway,
I will check it again.
Thanks you,
Olaf
Best regards,
Ana
On Sat, Jun 27, 2015 at 4:38 AM, olx69 ope-li...@gmx.de
mailto:ope-li...@gmx.de wrote:
Hello Ana,
I´m not sure about this, but I noticed something about the names for
your storage:
---bacula-traymon.conf--
Storage {
Name = bacula-tux64-sd
...
}
bacula-dir-full.conf
Storage {
Name = File
...
}
bacula-sd-full.conf-
Storage { # definition of myself
Name = bacula-tux64-sd
...
}
Could you try Name = bacula-tux64-sd in your bacula-dir-full.conf or
Name = File in your bacula-traymon.conf for the storage definition?
If I change this but 'bat' doesn't work any more (probably bconsole too
- not tested). Also it doesn't change the behaviour of traymonitor.
I had a look at the original bacula-dir.conf, e.g.
# Definition of a second file Virtual Autochanger device
# Possibly pointing to a different disk drive
Storage {
Name = File2
# Do not use localhost here
Address = localhost# N.B. Use a fully qualified
name here
SDPort = 9103
Password = @@SD_PASSWORD@@
Device = FileChgr2
Media Type = File2
Maximum Concurrent Jobs = 10# run up to 10 jobs a the
same time
}
so this seems to be correct.
Also I notice a warning:
26-Jun 19:36 bacula-tux64-dir: Warning: Cannot bind port 9101: ERR=Die
angeforderte Adresse kann nicht zugewiesen werden: Retrying ...
english: Can't assign requested address. Retrying ...
Maybe it's relevant.
This configuration did work with bacula 5.x, I was not aware of thise
changes in 7.x. Maybe v5.x was more sloppy with config files ...
Thank you,
Olaf
Best regards,
Ana
On Fri, Jun 26, 2015 at 2:36 AM, olx69 ope-li...@gmx.de
mailto:ope-li...@gmx.de
mailto:ope-li...@gmx.de mailto:ope-li...@gmx.de wrote:
Hello Ane,
Sorry I was out a few days Have you tested your Bacula with
these
fake passwords? Or you have just changed them for posting here?
I
found no errors in your passwords configurations, but I'm not
sure if
you are using these ones posted here. In the case you're not,
could you
verify your director to storage daemon password configuration
(not the
one for communicating with monitor)? The error message points to a
mismatch here.
No, these are my real passwords! I trust in my secure LAN ;-)
Thank you,
Olaf
On Tue, Jun 23, 2015 at 11:04 AM, olx69 ope-li...@gmx.de
mailto:ope-li...@gmx.de mailto:ope-li...@gmx.de
mailto:ope-li...@gmx.de
mailto:ope-li...@gmx.de mailto:ope-li...@gmx.de
mailto:ope-li...@gmx.de mailto:ope-li...@gmx.de wrote:
Am 18.06.2015 um 16:13 schrieb olx69:
Hello Ana,
Sorry I'm late in this post.
It seems there is still some password mismatching
problems.
Could you
post your resources definitions for monitor (in
bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf) and your
tray-monitor.conf?
thank you for investigating! attached the files,
no idea? Here the reduced password related part. Imo
all is
correct,
isn't it?
---bacula-traymon.conf--
Monitor {
Name = bacula-tux64-mon
Password = MON_DIR_PASSWORD # password
for the
Directors
RefreshInterval = 3 seconds
}
Client {
Name = bacula-tux64-fd
Address = tux64.home.lan
Password = MON_FD_PASSWORD # password for
FileDaemon
}
Storage {
Name = bacula-tux64-sd
Address = tux64.home.lan
Password = MON_SD_PASSWORD # password for
StorageDaemon
}
Director
Re: [Bacula-users] Could not connect to server Director daemon ....
Hello Ana,
I´m not sure about this, but I noticed something about the names for
your storage:
---bacula-traymon.conf--
Storage {
Name = bacula-tux64-sd
...
}
bacula-dir-full.conf
Storage {
Name = File
...
}
bacula-sd-full.conf-
Storage { # definition of myself
Name = bacula-tux64-sd
...
}
Could you try Name = bacula-tux64-sd in your bacula-dir-full.conf or
Name = File in your bacula-traymon.conf for the storage definition?
If I change this but 'bat' doesn't work any more (probably bconsole too
- not tested). Also it doesn't change the behaviour of traymonitor.
I had a look at the original bacula-dir.conf, e.g.
# Definition of a second file Virtual Autochanger device
# Possibly pointing to a different disk drive
Storage {
Name = File2
# Do not use localhost here
Address = localhost# N.B. Use a fully qualified name here
SDPort = 9103
Password = @@SD_PASSWORD@@
Device = FileChgr2
Media Type = File2
Maximum Concurrent Jobs = 10# run up to 10 jobs a the same time
}
so this seems to be correct.
Also I notice a warning:
26-Jun 19:36 bacula-tux64-dir: Warning: Cannot bind port 9101: ERR=Die
angeforderte Adresse kann nicht zugewiesen werden: Retrying ...
english: Can't assign requested address. Retrying ...
Maybe it's relevant.
This configuration did work with bacula 5.x, I was not aware of thise
changes in 7.x. Maybe v5.x was more sloppy with config files ...
Thank you,
Olaf
Best regards,
Ana
On Fri, Jun 26, 2015 at 2:36 AM, olx69 ope-li...@gmx.de
mailto:ope-li...@gmx.de wrote:
Hello Ane,
Sorry I was out a few days Have you tested your Bacula with these
fake passwords? Or you have just changed them for posting here? I
found no errors in your passwords configurations, but I'm not sure if
you are using these ones posted here. In the case you're not, could you
verify your director to storage daemon password configuration (not the
one for communicating with monitor)? The error message points to a
mismatch here.
No, these are my real passwords! I trust in my secure LAN ;-)
Thank you,
Olaf
On Tue, Jun 23, 2015 at 11:04 AM, olx69 ope-li...@gmx.de
mailto:ope-li...@gmx.de
mailto:ope-li...@gmx.de mailto:ope-li...@gmx.de wrote:
Am 18.06.2015 um 16:13 schrieb olx69:
Hello Ana,
Sorry I'm late in this post.
It seems there is still some password mismatching problems.
Could you
post your resources definitions for monitor (in
bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf) and your
tray-monitor.conf?
thank you for investigating! attached the files,
no idea? Here the reduced password related part. Imo all is
correct,
isn't it?
---bacula-traymon.conf--
Monitor {
Name = bacula-tux64-mon
Password = MON_DIR_PASSWORD # password for the
Directors
RefreshInterval = 3 seconds
}
Client {
Name = bacula-tux64-fd
Address = tux64.home.lan
Password = MON_FD_PASSWORD # password for
FileDaemon
}
Storage {
Name = bacula-tux64-sd
Address = tux64.home.lan
Password = MON_SD_PASSWORD # password for
StorageDaemon
}
Director {
Name = bacula-tux64-dir
Address = tux64.home.lan
}
bacula-dir-full.conf
Director {
Name = bacula-tux64-dir
Password = DIR_PASSWORD# BConsole password
}
Console {
Name = bacula-tux64-mon
Password = MON_DIR_PASSWORD
...
}
Client {
Name = bacula-tux64-fd
Password = FD_PASSWORD# password for FileDaemon
...
}
-bacula-fd-full.conf-
Director {
Name = bacula-tux64-dir
Password = FD_PASSWORD
}
Director {
Name = bacula-tux64-mon
Password = MON_FD_PASSWORD
}
bacula-sd-full.conf-
Director {
Name = bacula-tux64-dir
Password = SD_PASSWORD
}
Director {
Name = bacula-tux64-mon
Password = MON_SD_PASSWORD
...
}
--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network
Re: [Bacula-users] Could not connect to server Director daemon ....
Hello Ane,
Sorry I was out a few days Have you tested your Bacula with these
fake passwords? Or you have just changed them for posting here? I
found no errors in your passwords configurations, but I'm not sure if
you are using these ones posted here. In the case you're not, could you
verify your director to storage daemon password configuration (not the
one for communicating with monitor)? The error message points to a
mismatch here.
No, these are my real passwords! I trust in my secure LAN ;-)
Thank you,
Olaf
On Tue, Jun 23, 2015 at 11:04 AM, olx69 ope-li...@gmx.de
mailto:ope-li...@gmx.de wrote:
Am 18.06.2015 um 16:13 schrieb olx69:
Hello Ana,
Sorry I'm late in this post.
It seems there is still some password mismatching problems.
Could you
post your resources definitions for monitor (in bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf) and your tray-monitor.conf?
thank you for investigating! attached the files,
no idea? Here the reduced password related part. Imo all is correct,
isn't it?
---bacula-traymon.conf--
Monitor {
Name = bacula-tux64-mon
Password = MON_DIR_PASSWORD # password for the Directors
RefreshInterval = 3 seconds
}
Client {
Name = bacula-tux64-fd
Address = tux64.home.lan
Password = MON_FD_PASSWORD # password for FileDaemon
}
Storage {
Name = bacula-tux64-sd
Address = tux64.home.lan
Password = MON_SD_PASSWORD # password for StorageDaemon
}
Director {
Name = bacula-tux64-dir
Address = tux64.home.lan
}
bacula-dir-full.conf
Director {
Name = bacula-tux64-dir
Password = DIR_PASSWORD# BConsole password
}
Console {
Name = bacula-tux64-mon
Password = MON_DIR_PASSWORD
...
}
Client {
Name = bacula-tux64-fd
Password = FD_PASSWORD# password for FileDaemon
...
}
-bacula-fd-full.conf-
Director {
Name = bacula-tux64-dir
Password = FD_PASSWORD
}
Director {
Name = bacula-tux64-mon
Password = MON_FD_PASSWORD
}
bacula-sd-full.conf-
Director {
Name = bacula-tux64-dir
Password = SD_PASSWORD
}
Director {
Name = bacula-tux64-mon
Password = MON_SD_PASSWORD
...
}
--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical virtual servers, alerts via email sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
mailto:Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical virtual servers, alerts via email sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Could not connect to server Director daemon ....
Am 18.06.2015 um 16:13 schrieb olx69:
Hello Ana,
Sorry I'm late in this post.
It seems there is still some password mismatching problems. Could you
post your resources definitions for monitor (in bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf) and your tray-monitor.conf?
thank you for investigating! attached the files,
no idea? Here the reduced password related part. Imo all is correct,
isn't it?
---bacula-traymon.conf--
Monitor {
Name = bacula-tux64-mon
Password = MON_DIR_PASSWORD # password for the Directors
RefreshInterval = 3 seconds
}
Client {
Name = bacula-tux64-fd
Address = tux64.home.lan
Password = MON_FD_PASSWORD # password for FileDaemon
}
Storage {
Name = bacula-tux64-sd
Address = tux64.home.lan
Password = MON_SD_PASSWORD # password for StorageDaemon
}
Director {
Name = bacula-tux64-dir
Address = tux64.home.lan
}
bacula-dir-full.conf
Director {
Name = bacula-tux64-dir
Password = DIR_PASSWORD# BConsole password
}
Console {
Name = bacula-tux64-mon
Password = MON_DIR_PASSWORD
...
}
Client {
Name = bacula-tux64-fd
Password = FD_PASSWORD# password for FileDaemon
...
}
-bacula-fd-full.conf-
Director {
Name = bacula-tux64-dir
Password = FD_PASSWORD
}
Director {
Name = bacula-tux64-mon
Password = MON_FD_PASSWORD
}
bacula-sd-full.conf-
Director {
Name = bacula-tux64-dir
Password = SD_PASSWORD
}
Director {
Name = bacula-tux64-mon
Password = MON_SD_PASSWORD
...
}
--
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical virtual servers, alerts via email sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Could not connect to server Director daemon ....
Hello Ana,
Sorry I'm late in this post.
It seems there is still some password mismatching problems. Could you
post your resources definitions for monitor (in bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf) and your tray-monitor.conf?
thank you for investigating! attached the files,
Olaf
Director {
Name = bacula-tux64-dir
Description = Main Bacula Director
DIRport = 9101
DirAddress = tux64.home.lan
QueryFile = /etc/bacula/query.sql
WorkingDirectory = /var/spool/bacula
#PidDirectory = /var/run/bacula
PidDirectory = /var/run
Maximum Concurrent Jobs = 1 # 1 because there is 1 storage devices. See
pools.conf, devices.conf
Password = DIR_PASSWORD # BConsole password
Messages = Daemon
}
Console {
Name = bacula-tux64-mon
Password = MON_DIR_PASSWORD
CommandACL = status, .status
}
Catalog {
Name = MyCatalog
dbname = bacula
user = bacula
password =
}
Client {
Name = tux32-fd
Address = tux32.home.lan
FDPort = 9102
Catalog = MyCatalog
Password = FD_PASSWORD_2 # password for FileDaemon 2
File Retention = 30 days# 30 days
Job Retention = 6 months# 6 months
AutoPrune = yes # Prune expired Jobs/Files
}
Client {
Name = bacula-tux64-fd
Address = tux64.home.lan
FDPort = 9102
Catalog = MyCatalog
Password = FD_PASSWORD# password for FileDaemon
File Retention = 30 days# 30 days
Job Retention = 6 months# 6 months
AutoPrune = yes # Prune expired Jobs/Files
}
FileSet {
Name = Full Set
Include {
Options {
signature = SHA1
compression = gzip
onefs = yes
}
File = /usr/bin
}
Exclude {
File = /var/spool/bacula
File = /proc
File = /tmp
File = /.journal
File = /.fsck
File = /sys
File = /dev
}
}
FileSet {
Name = Home Set
Include {
Options {
Exclude = yes
RegexDir = [cC]ache
RegexDir = \.gvfs/*
WildDir = *.thumbnails/*
WildDir = *.wine/*
WildDir = */CEWE/*
}
Options {
# no compression
signature = SHA1
ignore case = yes
WildFile = *.pdf
WildFile = *.odt
WildFile = *.ods
WildFile = *.jpg
WildFile = *.jpeg
WildFile = *.png
WildFile = *.gif
WildFile = *.mp3
WildFile = *.ogg
WildFile = *.avi
WildFile = *.mpg
WildFile = *.mpeg
WildFile = *.mp4
WildFile = *.mts
WildFile = *.flv
WildFile = *.swf
WildFile = *.mov
WildFile = *.gz
WildFile = *.tgz
WildFile = *.bz2
WildFile = *.tbz2
WildFile = *.z
WildFile = *.zip
WildFile = *.rar
}
Options {
# compression
signature = SHA1
compression = gzip
}
File = /home
File = /storage/home
ExcludeDirContaining = .no_backup
}
# exclude some dot files
#
http://askubuntu.com/questions/40992/what-files-and-directories-can-be-excluded-from-a-backup-of-the-home-directory
Exclude {
File = */.gvfs/*
File = */.local/share/gvfs-metadata/*
File = */.dbus/*
File = */.cache/*
File = */.cddb/*
File = */.fontconfig/*
# Flash-specific
File = */.adobe/*
File = */.macromedia/*
# other files
File = */.xsession-errors
File = */.Xauthority #
session-specific
File = */.ICEauthority
File = */.gksu.lock
File = */.pulse/*
File = */.pulse-cookie
File = */.esd_auth
File = */lost+found/*
# firefox specific
File = */.mozilla/firefox/*/Cache/*
File = */.mozilla/firefox/*/minidumps/* # in case Fx
crashes dumps will be stored in this
File = */.mozilla/firefox/*/.parentlock #
session-specific
File = */.mozilla/firefox/*/urlclassifier3.sqlite # phishing
database, recreated
File = */.mozilla/firefox/*/blocklist.xml # blacklisted
extensions
File = */.mozilla/firefox/*/extensions.sqlite
File = */.mozilla/firefox/*/extensions.sqlite-journal
File = */.mozilla/firefox/*/extensions.rdf
File = */.mozilla/firefox/*/extensions.ini
File = */.mozilla/firefox/*/extensions.cache
File = */.mozilla/firefox/*/XUL.mfasl # cached UI
data, recreated
File = */.mozilla/firefox/*/XPC.mfasl
File = */.mozilla/firefox/*/xpti.dat
File = */.mozilla/firefox/*/compreg.dat
File = */.mozilla/firefox/Crash Reports/*
# Google Chrome
File = */.config/google-chrome/Default/Local Storage/*
File = */.config/google-chrome/Default/Session Storage/*
File = */.config/google-chrome/Default/Application Cache/*
File = */.config/google-chrome/Default/History Index*
# GnuPGP
File = */.gnupg/rnd
File = */.gnupg/random_seed
File = */.gnupg/.#*
File = */.gnupg/*.lock
File = */.gnupg/gpg-agent-info-*
# DropBox
File = */.dropbox/*
Re: [Bacula-users] Could not connect to server Director daemon ....
Hello Anna,
I was not refering to the names for user and password. Instead, the
directives user and password for Catalog definition. I noticed in
your post that you defined Catalog using the keywords dbuser and
dbpassword, instead of using user and password. Like bellow:
Catalog {
Name = MyCatalog
dbname = bacula
dbuser = bacula
dbpassword =
}
ah, thank you for pointing this. There are some wrong blogs on web ...
Anyway, After some test this did not solve the problem - finally it
where problems with right group and permissions. Further I had to add my
FQN at /etc/hosts - something seems to be wrong at F22.
But two problems still resist:
$ bacula-tray-monitor -d99 -c /etc/bacula/tray-monitor.conf
tray-monitor: bsock.c:310-0 OK connected to server Director daemon
tux64.home.lan:9101.
tray-monitor: cram-md5.c:139-0 sending resp to challenge:
Y8UyU8/FHw+i68UHd4JUuB
tray-monitor: cram-md5.c:67-0 send: auth cram-md5 challenge
466579471.1434046447@tray-monitor ssl=0
tray-monitor: cram-md5.c:86-0 Authenticate OK w9kJdy/8Qy/Qt6/pf7+hLD
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:310-0 OK connected to server File daemon
tux64.home.lan:9102.
tray-monitor: cram-md5.c:139-0 sending resp to challenge:
+QpHgScKy9+uqmNV74+UXC
tray-monitor: cram-md5.c:67-0 send: auth cram-md5 challenge
1223422051.1434046447@tray-monitor ssl=0
tray-monitor: cram-md5.c:86-0 Authenticate OK fj+lV9YEWzdUqFgeP/+v6B
tray-monitor: bsock.c:310-0 OK connected to server Storage daemon
tux64.home.lan:9103.
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
11-Jun 20:14 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#SECTION0026
for help.
$ sudo bat -d99
X Error: BadAccess (attempt to access private resource denied) 10
Extension:130 (MIT-SHM)
Minor opcode: 1 (X_ShmAttach)
Resource id: 0x304
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension:130 (MIT-SHM)
Minor opcode: 3 (X_ShmPutImage)
Resource id: 0x3fa
bat: bsock.c:310-0 OK connected to server Director daemon
tux64.home.lan:9101.
bat: cram-md5.c:139-0 sending resp to challenge: Ww+Xo3EtyD/uKC+LC8+6rA
bat: cram-md5.c:67-0 send: auth cram-md5 challenge
628826973.1434046684@bat ssl=0
bat: cram-md5.c:86-0 Authenticate OK IW+T/R/05RcT4W+4R8+EhC
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)
X Error: BadShmSeg (invalid shared segment parameter) 128
Extension:130 (MIT-SHM)
Minor opcode: 3 (X_ShmPutImage)
Resource id: 0x3fa
and no widgets are drawn. Any hints? It this specific to Fedora22?
Thank you,
Olaf
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Could not connect to server Director daemon ....
Hello Ana,
Hello Olaf,
There are some directive keywords mismatch (user and password):
Catalog {
Name = MyCatalog
dbname = bacula
user = bacula
password =
}
it's SQLite3 DB, does the user/password matter? Even if I set the user =
it doesn't change it.
Thank you,
Olaf
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Could not connect to server Director daemon ....
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 tcp0 0 192.168.1.11:9101 0.0.0.0:* LISTEN 7933/bacula-dir tcp0 0 192.168.1.11:9102 0.0.0.0:* LISTEN 8195/bacula-fd tcp0 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#SECTION0026 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 tcp0 0 127.0.0.2:9101 0.0.0.0:* LISTEN 855/bacula-dir tcp0 0 127.0.0.2:9102 0.0.0.0:* LISTEN 857/bacula-fd tcp0 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
Re: [Bacula-users] Could not connect to server Director daemon ....
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 tcp0 0 192.168.1.11:9101 0.0.0.0:* LISTEN 7933/bacula-dir tcp0 0 192.168.1.11:9102 0.0.0.0:* LISTEN 8195/bacula-fd tcp0 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#SECTION0026 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Could not connect to server Director daemon ....
Hello Ana,
Your daemons are listening on 127.0.0.2, and bacula is trying to connect
on 198.162.1.11. You can configure Bacula to listen to any IP commenting
the lines: DirAddress, FDAddress and SDAddress in bacula-dir.conf,
bacula-fd.conf and bacula-sd.conf. Or you can check your DNS resolution.
Maybe the FQDN hostname is being resolved to a local IP.
A quick search on the config files got:
$ find . -name \*.conf -exec egrep -H -i Address {} \; | sed -e '/:#/d'
./bacula-dir.conf: DirAddress = tux64.home.lan
./bacula-sd.conf: SDAddress = tux64.home.lan
./bacula-dir.conf.d/storage.conf: Address = tux64.home.lan
./bacula-dir.conf.d/client-tux32.conf: Address = tux32.home.lan
./bacula-dir.conf.d/client-tux64.conf: Address = tux64.home.lan
./bconsole.conf: address = tux64.home.lan
./tray-monitor.conf: Address = tux64.home.lan
./tray-monitor.conf: Address = tux64.home.lan
./tray-monitor.conf: Address = tux64.home.lan
./bat.conf: address = tux64.home.lan
$ cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
$ hostname
tux64.home.lan
so, why does it bind to loopback device ip?
Have you changed your PID directory to /var/run after upgrade?
Can you
post the output of netstat -nltup | grep bacula?
$ sudo netstat -nltup | grep bacula
tcp0 0 127.0.0.2:9101 http://127.0.0.2:9101
0.0.0.0:* LISTEN
855/bacula-dir
tcp0 0 127.0.0.2:9102 http://127.0.0.2:9102
0.0.0.0:*
LISTEN 857/bacula-fd
tcp0 0 127.0.0.2:9103 http://127.0.0.2:9103
0.0.0.0:*
LISTEN 851/bacula-sd
Thank you,
Olaf
--
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Could not connect to server Director daemon ....
Hello,
since my upgrade from fedora 16 to 21/22 my bacula setup isn't working
any more. I did check the password problem as described at bacula's FAQ
and didn't found any reason for not working. Bacula is v 7.05 (as in
fedora 22).
I get per email the following:
Bacula: Backup Error of tux64-fd Full
03-Jun 19:30 bacula-tux64-dir JobId 286: shell command: run BeforeJob
/usr/libexec/bacula/make_catalog_backup.pl MyCatalog
03-Jun 19:30 bacula-tux64-dir JobId 286: BeforeJob: Can't find your
catalog (MyCatalog) in director configuration
03-Jun 19:30 bacula-tux64-dir JobId 286: Error: Runscript: BeforeJob
returned non-zero status=1. ERR=Child exited with code 1
or
Bacula: Backup Fatal Error of tux64-fd Incremental
03-Jun 19:00 bacula-tux64-dir JobId 285: Start Backup JobId 285,
Job=tux64_System.2015-06-03_18.30.01_03
03-Jun 19:00 bacula-tux64-dir JobId 285: Warning: bsock.c:112 Could not
connect to Storage daemon on tux64.home.lan:9103. ERR=Verbindungsaufbau
abgelehnt
Retrying ...
= Connection refused
Further by using console I get:
$ sudo bacula-tray-monitor -c /etc/bacula/tray-monitor.conf -d100
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:283-0 Could not connect to server Director daemon
tux64.home.lan:9101. ERR=Connection refused
tray-monitor: bsock.c:106-0 Unable to connect to Director daemon on
tux64.home.lan:9101. ERR=Connection refused
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:283-0 Could not connect to server File daemon
tux64.home.lan:9102. ERR=Connection refused
tray-monitor: bsock.c:106-0 Unable to connect to File daemon on
tux64.home.lan:9102. ERR=Connection refused
The services as such seems to work properly:
$ sudo systemctl status bacula-fd.service
● bacula-fd.service - Bacula-FileDaemon, a Backup-client
Loaded: loaded (/usr/lib/systemd/system/bacula-fd.service; enabled;
vendor preset: disabled)
Active: active (running) since Do 2015-06-04 15:56:31 CEST; 57min ago
Docs: man:bacula-fd(8)
Main PID: 847 (bacula-fd)
CGroup: /system.slice/bacula-fd.service
└─847 /usr/sbin/bacula-fd -f -c /etc/bacula/bacula-fd.conf
-u root -g root
Jun 04 15:56:31 tux64.home.lan systemd[1]: Started Bacula-FileDaemon, a
Backup-client.
Jun 04 15:56:31 tux64.home.lan systemd[1]: Starting Bacula-FileDaemon, a
Backup-client...
$ sudo systemctl status bacula-sd.service
● bacula-sd.service - Bacula-StorageDaemon, the storage-server
Loaded: loaded (/usr/lib/systemd/system/bacula-sd.service; enabled;
vendor preset: disabled)
Active: active (running) since Do 2015-06-04 15:56:31 CEST; 57min ago
Docs: man:bacula-sd(8)
Main PID: 851 (bacula-sd)
CGroup: /system.slice/bacula-sd.service
└─851 /usr/sbin/bacula-sd -f -c /etc/bacula/bacula-sd.conf
-u bacula -g tape
Jun 04 15:56:31 tux64.home.lan systemd[1]: Started Bacula-StorageDaemon,
the storage-server.
Jun 04 15:56:31 tux64.home.lan systemd[1]: Starting
Bacula-StorageDaemon, the storage-server...
$ sudo systemctl status bacula-dir.service
● bacula-dir.service - Bacula-Director, the Backup-server
Loaded: loaded (/usr/lib/systemd/system/bacula-dir.service; enabled;
vendor preset: disabled)
Active: active (running) since Do 2015-06-04 15:56:31 CEST; 58min ago
Docs: man:bacula-dir(8)
Main PID: 853 (bacula-dir)
CGroup: /system.slice/bacula-dir.service
└─853 /usr/sbin/bacula-dir -f -c /etc/bacula/bacula-dir.conf
-u bacula -g bacula
Jun 04 15:56:31 tux64.home.lan systemd[1]: Started Bacula-Director, the
Backup-server.
Jun 04 15:56:31 tux64.home.lan systemd[1]: Starting Bacula-Director, the
Backup-server...
Attached my compressed configs. What went wrong here?
Thanks,
Olaf
Director {
Name = bacula-tux64-dir
Description = Main Bacula Director
DIRport = 9101
DirAddress = tux64.home.lan
QueryFile = /etc/bacula/query.sql
WorkingDirectory = /var/spool/bacula
#PidDirectory = /var/run/bacula
PidDirectory = /var/run
Maximum Concurrent Jobs = 1 # 1 because there is 1 storage devices. See
pools.conf, devices.conf
Password = DIR_PASSWORD # BConsole password
Messages = Daemon
}
Console {
Name = bacula-tux64-mon
Password = MON_DIR_PASSWORD
CommandACL = status, .status
}
Catalog {
Name = MyCatalog
dbname = bacula
dbuser = bacula
dbpassword =
}
Client {
Name = tux32-fd
Address = tux32.home.lan
FDPort = 9102
Catalog = MyCatalog
Password = FD_PASSWORD_2 # password for FileDaemon 2
File Retention = 30 days# 30 days
Job Retention = 6 months# 6 months
