Fatal error: Authorization key rejected by File Daemon
Cairo Campos
I created a lab with Bareos for studies, but when generating the backup via bconsole, the following errors are shown:
bareos-dir JobId 9: Fatal error: Authorization key rejected by File Daemon lenovo-pc-fd.
Please see http://doc.bareos.org/master/html/bareos-manual-main-reference.html#AuthorizationErrors for help.
bareos-dir JobId 9: Fatal error: No Job status returned from FD.
bareos-dir JobId 9: Error: Bareos bareos-dir 16.2.4 (01Jul16):
Build OS: x86_64-pc-linux-gnu debian Debian GNU/Linux 8.0 (jessie)
JobId: 9
Job: lenovo-pc.2017-10-16_17.37.17_04
Backup Level: Full (upgraded from Incremental)
Client: "lenovo-pc-fd"
FileSet: "lenovo-pc" 2017-10-16 00:14:11
Pool: "Full" (From Job FullPool override)
Catalog: "MyCatalog" (From Client resource)
Storage: "File" (From Job resource)
Scheduled time: 16-Out-2017 17:37:13
Start time: 16-Out-2017 17:37:19
End time: 16-Out-2017 17:37:25
Elapsed time: 6 secs
Priority: 10
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: 1
Volume Session Time: 1508182618
Last Volume Bytes: 0 (0 B)
Non-fatal FD errors: 2
SD Errors: 0
FD termination status: Error
SD termination status: Waiting on FD
FD Secure Erase Cmd:
Termination: *** Backup Error ***
I already changed the password, but it did not work! :(
What should I do?
Alexander Kushnirenko
1. In director check /etc/bareos/bareos-dir.d/client/XXXXX.conf check password
On client check /etc/bareos/bareos-fd.d/director/bareos-dir.conf - check password (You can use matching passwords and not use [md5])
2. You can cross check that director is talking to FD using "status client=...." command in bconsole
3. Then similarly check that FD can talk to Storage Daemon.
понедельник, 16 октября 2017 г., 22:51:58 UTC+3 пользователь Cairo Campos написал:
Cairo Campos
Hello, I configured the Windows client according to the settings of the attached image (ConfigClientWindows.JPG).
Later I created the /etc/bareos/bareos-dir.d/client/lenovo-pc-fd.conf file:
Client {
Name = lenovo-pc-fd
Address = 192.168.88.14
Password = "w80SRCR4MgMdgJWXH1qsB4Ec/yJSE/Xc/vdlQeXeVj0/"
# uncomment the following if using bacula
# Catalog = "MyCatalog"
}
Other Settings:
/etc/bareos/bareos-dir.d/director/bareos-dir.conf
Director {
Name = bareos-dir
QueryFile = "/usr/lib/bareos/scripts/query.sql"
Maximum Concurrent Jobs = 10
Password = "Y3GEj/U9e0TiWlIM78NBra3QFMXZEBMTzRc/2Eh9y0U4"
Messages = Daemon
Auditing = yes
}
/etc/bareos/bareos-fd.d/director/bareos-dir.conf
Director {
Name = bareos-dir
Password = "EhBoEFCPkKqnGHA0GIhFYD9TbFrmMGaJKbDXOsYLHv5/"
Description = "Allow the configured Director to access this file daemon."
}
When using bconsole I could see that the synchronization was not possible:
root@bareos:/etc/bareos/bareos-dir.d/jobdefs# bconsole
Connecting to Director localhost:9101
1000 OK: bareos-dir Version: 16.2.4 (01 July 2016)
Enter a period to cancel a command.
*status client=
Error: Client resource does not exist.
The defined Client resources are:
1: lenovo-pc-fd
2: bareos-fd
Select Client (File daemon) resource (1-2): 1
Connecting to Client lenovo-pc-fd at 192.168.88.14:9102
Failed to connect to Client lenovo-pc-fd.
Jörg Steffens
You can check from command line via
netcat -v 192.168.88.14 9102
You should receive something like:
Connection to ... 9102 port [tcp/bacula-fd] succeeded!
If yes, verify that the client password is identical on server and client.
On server it is in the file
/etc/bareos/bareos-dir.d/client/lenovo-pc-fd.conf
On the Windows Client I assume it is somewhere at
c:\ProgramData\Bareos\bareos-fd.d\director\bareos-dir.conf
Both password entry must be identical. When changing it, the Windows
bareos-fd must be restarted. On the bareos server, a reload from
bconsole will suffice.
--
Jörg Steffens joerg.s...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 630693-91
http://www.bareos.com Fax: +49 221 630693-10
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer:
S. Dühr, M. Außendorf, Jörg Steffens, P. Storz
Alexander Kushnirenko
--
You received this message because you are subscribed to a topic in the Google Groups "bareos-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bareos-users/drBaKDqD_ss/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bareos-users+unsubscribe@googlegroups.com.
To post to this group, send email to bareos...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Cairo Campos
Result of the command netcat:
root@bareos:/home/server# netcat -v 192.168.88.14 9102
192.168.88.14: inverse host lookup failed: Unknown host
(UNKNOWN) [192.168.88.14] 9102 (bacula-fd) : Connection timed out
File settings:
/etc/bareos/bareos-dir.d/client/lenovo-pc-fd.conf
Client {
Name = lenovo-pc-fd
Address = 192.168.88.14
Password = "w80SRCR4MgMdgJWXH1qsB4Ec/yJSE/Xc/vdlQeXeVj0/"
# uncomment the following if using bacula
# Catalog = "MyCatalog"
}
c:\ProgramData\Bareos\bareos-fd.d\director\bareos-dir.conf
Director {
Name = bareos-dir
Password = "rLKCwUJzqVUXvGgLT3yugXyvVHADnDlELcQgC/lP4sQ3"
Description = "Allow the configured Director to access this file daemon."
}
Even putting the same password on both files, the problem continued.
Attached network configuration of windows machine (ConfigNetWindows.JPG)
Cairo Ap Campos
--
You received this message because you are subscribed to a topic in the Google Groups "bareos-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/bareos-users/drBaKDqD_ss/unsubscribe.
To unsubscribe from this group and all its topics, send an email to bareos-users+unsubscribe@googlegroups.com.
To post to this group, send email to bareos...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Cairo Aparecido Campos
_________________________________________________
Currículo Lattes: http://lattes.cnpq.br/2433921004365040