Re: [Bacula-users] Error sending Hello to File daemon


On 13. Feb, 2013, at 10:54 PM, Cristian Livadaru <cristian AT lcx DOT at> wrote:

> I have a issue I can't seem to figure out. 
> configured a bacula server v5.2.12 and a first client, both running Debian 
> Squeeze 
> 
> Client {
>  Name = client1.foo.com-fd
>  Address = client1.foo.com
>  FDPort = 9102
>  Catalog = MyCatalog
>  Password = "very secret"
>  File Retention = 30 days
>  Job Retention = 6 months
>  AutoPrune = yes
> }
> 
> Job {
>  Name = "Backup client1.foo.com"
>  Client = client1.foo.com-fd
>  JobDefs = "DefaultJob"
>  Write Bootstrap = "/var/lib/bacula/client1.foo.com.bsr"
> }
> 
> 
> The Backup for this client is working just fine. 
> I then copied this config and installed the same bacula version on a second 
> client. 
> 
> Client {
>  Name = client2.foo.com-fd
>  Address = client2.foo.com
>  FDPort = 9102
>  Catalog = MyCatalog
>  Password = "other secret pass"
>  File Retention = 30 days
>  Job Retention = 6 months
>  AutoPrune = yes
> }
> 
> Job {
>  Name = "Backup client2.foo.com"
>  Client = client2.foo.com-fd
>  JobDefs = "DefaultJob"
>  Write Bootstrap = "/var/lib/bacula/client2.foo.com.bsr"
> }
> 
> but this one doesn't work. 
>> From bcsonsole I tried to estimate a backup and I just receive an error. 
> 
> 13-Feb 22:20 backup.domain.com-dir JobId 0: Fatal error: Error sending Hello 
> to File daemon at "client2.foo.com:9102". ERR=Connection reset by peer
> 13-Feb 22:21 backup.domain.com-dir JobId 0: Fatal error: Unable to 
> authenticate with File daemon at "client2.foo.com:9102". Possible causes:
> Passwords or names not the same or
> Maximum Concurrent Jobs exceeded on the FD or
> FD networking messed up (restart daemon).
> Please see 
> http://www.bacula.org/en/rel-manual/Bacula_Freque_Asked_Questi.html#SECTION003760000000000000000
>  for help.
> 
> funny thing is, as soon as I do a estimate for client 2, I can't do a 
> estimate for client 1 anymore! 
> I always keep getting the error message for client 2! 
> If I restart the director, estimate for client 1 works again until I do a 
> estimate for client 2. 
> 
> I started fd with debug level 999 on client2 and this is what I got: 
> 
> client2.foo.com-fd: bnet.c:766-0 who=client host=214.15.107.22 port=9102
> client2.foo.com-fd: jcr.c:904-0 set_jcr_job_status(*System*, C)
> client2.foo.com-fd: jcr.c:913-0 OnEntry JobStatus=client2.foo.com-fd: 
> jcr.c:924-0 Set new stat. old: client2.foo.com-fd: jcr.c:929-0 leave 
> setJobStatus old=client2.foo.com-fd: find.c:81-0 init_find_files ff=16789d8
> client2.foo.com-fd: job.c:270-0 <dird: Hello Director backup.foo.com-dir 
> calling
> client2.foo.com-fd: job.c:286-0 Executing Hello command.
> client2.foo.com-fd: job.c:436-0 Calling Authenticate
> client2.foo.com-fd: message.c:1255-0 Enter Jmsg type=3
> client2.foo.com-fd: message.c:725-0 Enter dispatch_msg type=3 
> msg=client2.foo.com-fd: Fatal Error at authenticate.c:208 because:
> Unable to authenticate Director
> client2.foo.com-fd: message.c:924-0 DIRECTOR for following msg: 
> client2.foo.com-fd: Fatal Error at authenticate.c:208 because:
> Unable to authenticate Director
> client2.foo.com-fd: message.c:929-0 no jcr for following msg: 
> client2.foo.com-fd: Fatal Error at authenticate.c:208 because:
> Unable to authenticate Director
> client2.foo.com-fd: job.c:289-0 Quit command loop. Canceled=0
> client2.foo.com-fd: runscript.c:108-0 runscript: running all RUNSCRIPT object 
> (ClientAfterJob) JobStatus=C
> client2.foo.com-fd: job.c:399-0 Calling term_find_files
> client2.foo.com-fd: job.c:404-0 Done with term_find_files
> client2.foo.com-fd: runscript.c:286-0 runscript: freeing all RUNSCRIPTS object
> client2.foo.com-fd: message.c:503-0 Close_msg jcr=1678088
> client2.foo.com-fd: message.c:503-0 Close_msg jcr=0
> client2.foo.com-fd: message.c:523-0 ===Begin close msg resource at 165c188
> client2.foo.com-fd: message.c:608-0 Done walking message chain.
> client2.foo.com-fd: message.c:615-0 ===End close msg resource
> client2.foo.com-fd: job.c:406-0 Done with free_jcr
> client2.foo.com-fd: mem_pool.c:375-0 garbage collect memory pool
> 
> 
> as far as I can't see why it's Unable to authenticate Director but I have no 
> clue why. 
> Any hints please? 
> 
> Cris 
> ------------------------------------------------------------------------------

Found it, I was really blind yesterday. Looking exactly at the error and 
couldn't see the difference between client1 and client2.
On client1 I set the director name correctly to backup.foo.com on client2 I 
left it as it was installed, client2.foo.com which can not work! 
Everything works as expected now. 

Cris 


------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users