>>>>> On Wed, 01 May 2013 19:50:03 +0200, Erik P Olsen said:
> 
> On 01/05/13 17:30, Martin Simmons wrote:
> >>>>>> On Wed, 01 May 2013 16:40:09 +0200, Erik P Olsen said:
> >>
> >> On 17/04/13 09:24, Simone Caronni wrote:
> >>> Have you installed 5.2.13 on your own, from the updates-testing 
> >>> repository [1]
> >>> or from my repository [2]?
> >>>
> >>> Can you please check the last part of the file
> >>>
> >>> /usr/share/doc/bacula-common-5.2.13/README.Redhat
> >>>
> >>> and see if it's a permission problem on the /etc/bacula directory?
> >>>
> >>> [1]
> >>> https://admin.fedoraproject.org/updates/FEDORA-2013-5182/bacula-docs-5.2.13-2.fc18,bacula-5.2.13-8.fc18
> >>> [2] http://repos.fedorapeople.org/repos/slaanesh/bacula/
> >>>
> >>
> >> [snip]
> >>
> >> I am still hit by this authentication problem. I've checked the readme and 
> >> there
> >> is no permission problem on the /etc/bacula directory. It looks to me as if
> >> cram-md5 authentication is in error. I can show lots of messages but shall 
> >> for
> >> the moment list following few lines which may give an indication as to 
> >> what the
> >> problem is:
> >>
> >> epohost-sd: cram-md5.c:72-0 send: auth cram-md5
> >> <958993904.1367415842@epohost-sd> ssl=0
> >> epohost-sd: cram-md5.c:88-0 Bnet receive challenge response comm error.
> >> ERR=Connection reset by peer
> >> epohost-sd: authenticate.c:235-0 Challenge cram-auth failed with client
> >> epohost-sd: job.c:260-0 Authentication failed Job 
> >> ulla-pc.2013-05-01_15.43.59_10
> >>
> >> Authentication works fine on linux client it is just the windows client 
> >> that fails.
> >>
> >> If someone knows what is wrong, please let me know.
> >
> > "Connection reset by peer" means that the other end (or something in 
> > between)
> > has closed the connection, so I would look for logs on the client and/or any
> > route/firewall between the sd and the client.
> >
> > Does the "status client" command work on the Director?
> >
> > __Martin
> 
> Apparently:
> 
> Select Client (File daemon) resource (1-2): 2
> Connecting to Client ullapc-fd at Ulla-PC.epolan.dk:9102
> 
> ullapc-fd Version: 6.0.6 (30 September 2012)  VSS Linux Cross-compile Win32
> Daemon started 01-May-13 15:41. Jobs: run=0 running=0.
> Microsoft Windows 7 Home Premium Edition Service Pack 1 (build 7601), 32-bit
>   Heap: heap=0 smbytes=20,259 max_bytes=24,350 bufs=57 max_bufs=124
>   Sizes: boffset_t=8 size_t=4 debug=0 trace=1 mode=0,2010 bwlimit=0kB/s

OK, so try collecting a log from the client when it fails to authenticate.  I
think you have to use setdebug level=... trace=1 to make it write the log file
on Windows.

__Martin

------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users