This is happened to two new machines running CentOS 4.4. In the logs it says
SD termination status: Waiting on FD
Here is my settings on one of them.
Client {
Name = hl72
Address = 192.168.1.3
FDPort = 9102
Catalog = MyCatalog
Password = "bacula" # password for FileDaemon
}
Pool {
Name = hl72_Full
Pool Type = Backup
Recycle = yes
AutoPrune = yes
Volume Retention = 12h
Maximum Volume Jobs = 1
Label Format = "${Job}_${Level}"
Maximum Volumes = 6
}
Job {
Name = "hl72"
JobDefs = "hl72"
Write Bootstrap = "/etc/bacula/bootstrap/hl72.bsr"
}
JobDefs {
Name = "hl72
Type = Backup
Client = hl72
FileSet = "Default"
Schedule = "DailyCycle"
Storage = Storage_hl72
messages = Standard
Pool = hl72_Full
Priority = 5
}
Storage {
Name = Storage_hl72
# Do not use "localhost" here
Address = my.hostname.domainname.com # N.B. Use a fully
qualified name here
SDPort = 9103
Password = "bacula"
Device = Backup_hl72
Media Type = File
Autochanger = no
}
I have a couple more machines to setup but I need the above to work. I
followed what the documentation said. Is there a specific version of the
bacula-client that CentOS prefers. I am using version 1.36.2 of bacula-dir
and 1.36.3-1 of the bacula-client. I have even modified hl72's host file to
make sure it knows how to get the the director and I still have this
problem.
Any help would be appreciated.
Mike V
--
View this message in context:
http://www.nabble.com/Unable-to-Connect-fo-File-daemon.--ERR%3ANo-Route-to-host-tf3619783.html#a10107377
Sent from the Bacula - Users mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
