Fatal error: Unable to authenticate with File daemon at "192.168.1.222:9102".

1,285 views
Skip to first unread message

PH

unread,
Nov 10, 2013, 10:47:01 AM11/10/13
to bareos...@googlegroups.com
Hi,

I switched Bacula 5.2.12 to Bareos 12.4.4 and my problem is DIR is unable to authenticate with FD, I double checked names and passwords. It is not the network problem, I can telnet from DIR do FD 9102 port and from FD to DIR 9101 port.

My DIR config:

Director {
Name = server-dir
DIRport = 9101
QueryFile = "/usr/lib/bareos/scripts/query.sql"
Password = "password"
Messages = Daemon
Maximum Concurrent Jobs = 20
}

Client {
Name = client-fd
Address = 192.168.1.222
FDPort = 9102
Password = "password"
Maximum Concurrent Jobs = 20
}

My Win 7 FD (winbareos-12.4.4-64-bit-r510.3.exe) config:

Director {
Name = server-dir
Password = "password"
}

FileDaemon {
Name = client-fd
FDport = 9102
Maximum Concurrent Jobs = 20
}

Any idea please?

Thanks

Bruno Friedmann

unread,
Nov 10, 2013, 1:06:43 PM11/10/13
to bareos...@googlegroups.com
Figthing with same shit ...
My Advise try to change the password to a new one on the both side

openssl rand -rand /dev/urandom -base64 32
will create a new one to you.

I can't believe it is the case, but it is :-(


--

Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch

openSUSE Member
GPG KEY : D5C9B751C4653227
irc: tigerfoot

PH

unread,
Nov 11, 2013, 4:11:45 AM11/11/13
to bareos...@googlegroups.com
Dne neděle, 10. listopadu 2013 19:06:43 UTC+1 Bruno Friedmann napsal(a):
Hi, thanks for reply. The change of password didn't help me. The bareos client was in some bad state, so I uninstalled client, rebooted and installed again and it is working now.

Luis Candia

unread,
Nov 29, 2013, 10:13:40 AM11/29/13
to bareos...@googlegroups.com
Hi, I also have this issue, I have solved it copying the password thats is generated for the client when you execute the wizard on the client( Win7) and copy it on the Director's file on the server where is you client config section. I suggest you to config tray monitor to check if you may have a port blocking issue.
Reply all
Reply to author
Forward
0 new messages