Re: [Bacula-users] Hostname not found

On 02/10/2017 05:02 PM, Dan Langille wrote:
>>>> NOTE: this message is not about resolving the permissions error.  It is
>>>> about [what appears to be] a DNS issue.
>>>> 
>>>> Please help me understand which hostname is not being resolved in these
>>>> messages.  My checks with dig to verify DNS have found no errors.
>>>> 
>>>> I have checked:
>>>> 
>>>> Client:                 crey-fd
>>>> Read Storage:           "bacula-sd-01-file"
>>>> Write Storage:          "tape01" (From Job resource)
>>>> 
>>>> I've checked the bacula configuration files, looked for the Address, and
>>>> run 'dig +short' on the hostname
>>>> 
>>>> Then, with the IP address from the previous dig, I do 'dig +short -x'.
>>>> I get the original hostname.
>>>> 
>>>> Ideas please?
>>>> 
>>>> 
>>>> 
>>>> First email:
>>>> ###
>>>> 10-Feb 15:17 bacula-dir JobId 256313: Warning: FileSet MD5 digest not
>>>> found.
>>>> 10-Feb 15:17 bacula-dir JobId 256313: The following 1 JobId was chosen
>>>> to be copied: 255998
>>>> 10-Feb 15:17 bacula-dir JobId 256313: Copying using JobId=255998
>>>> Job=slocum_jail_snapshots.2017-02-05_03.04.00_46
>>>> 10-Feb 15:17 bacula-dir JobId 256313: Bootstrap records written to
>>>> /usr/local/bacula/working/bacula-dir.restore.27.bsr
>>>> 10-Feb 15:17 bacula-dir JobId 256313: Start Copying JobId 256313,
>>>> Job=CopyToTape-Full-LTO4.2017-02-10_15.17.52_17
>>>> 10-Feb 15:17 bacula-dir JobId 256313: Using Device "vDrive-0" to read.
>>>> 10-Feb 15:17 bacula-sd-01-sd JobId 256313: Ready to read from volume
>>>> "FullAuto-1369" on file device "vDrive-0" (/usr/local/bacula/volumes).
>>>> 10-Feb 15:17 bacula-sd-01-sd JobId 256313: Forward spacing Volume
>>>> "FullAuto-1369" to file:block 0:214.
>>>> 10-Feb 15:18 bacula-sd-01-sd JobId 256313: Error: bsock.c:453 Wrote 3814
>>>> bytes to client:Hostname not found:9103, but only 0 accepted.
>>>> 10-Feb 15:18 bacula-sd-01-sd JobId 256313: Fatal error: read.c:284 Error
>>>> sending to File daemon. ERR=Broken pipe
>>>> 10-Feb 15:18 bacula-sd-01-sd JobId 256313: Elapsed time=00:00:08,
>>>> Transfer rate=14.46 K Bytes/second
>>>> 10-Feb 15:18 bacula-sd-01-sd JobId 256313: Error: bsock.c:375 Socket has
>>>> errors=1 on call to client:Hostname not found:9103
>>>> 10-Feb 15:18 bacula-sd-01-sd JobId 256313: Fatal error: fd_cmds.c:142
>>>> Read data not accepted
>>>> 10-Feb 15:18 bacula-sd-01-sd JobId 256313: Error: bsock.c:375 Socket has
>>>> errors=1 on call to client:Hostname not found:9103
>>>> 10-Feb 15:18 bacula-dir JobId 256313: Error: Bacula bacula-dir 7.4.4
>>>> (28Sep16):
>>>> Build OS:               amd64-portbld-freebsd11.0 freebsd 11.0-RELEASE-p6
>>>> Prev Backup JobId:      255998
>>>> Prev Backup Job:        slocum_jail_snapshots.2017-02-05_03.04.00_46
>>>> New Backup JobId:       256314
>>>> Current JobId:          256313
>>>> Current Job:            CopyToTape-Full-LTO4.2017-02-10_15.17.52_17
>>>> Backup Level:           Full
>>>> Client:                 crey-fd
>>>> FileSet:                "EmptyCopyToTape" 2011-02-20 20:53:31
>>>> Read Pool:              "FullFile" (From Job resource)
>>>> Read Storage:           "bacula-sd-01-file" (From Pool resource)
>>>> Write Pool:             "FullsLTO4" (From Job resource)
>>>> Write Storage:          "tape01" (From Job resource)
>>>> Catalog:                "MyCatalog" (From Client resource)
>>>> Start time:             10-Feb-2017 15:17:55
>>>> End time:               10-Feb-2017 15:18:05
>>>> Elapsed time:           10 secs
>>>> Priority:               430
>>>> SD Files Written:       9
>>>> SD Bytes Written:       115,699 (115.6 KB)
>>>> Rate:                   11.6 KB/s
>>>> Volume name(s):
>>>> Volume Session Id:      98
>>>> Volume Session Time:    1486562541
>>>> Last Volume Bytes:      0 (0 B)
>>>> SD Errors:              3
>>>> SD termination status:  Error
>>>> Termination:            *** Copying Error ***
>>>> ###
>>>> 
>>>> Second email, which corresponds to the above copy job:
>>>> ###
>>>> 10-Feb 15:17 bacula-dir JobId 256314: Using Device "LTO_0" to write.
>>>> 10-Feb 15:17 tape01-sd JobId 256314: 3991 Bad autochanger "loaded? drive
>>>> 0" command: ERR=Child exited with code 1.
>>>> Results=cannot open SCSI device '/dev/pass3' - Permission denied
>>>> 
>>>> 10-Feb 15:17 tape01-sd JobId 256314: 3991 Bad autochanger "loaded? drive
>>>> 0" command: ERR=Child exited with code 1.
>>>> Results=cannot open SCSI device '/dev/pass3' - Permission denied
>>>> 
>>>> 10-Feb 15:18 tape01-sd JobId 256314: 3991 Bad autochanger "loaded? drive
>>>> 0" command: ERR=Child exited with code 1.
>>>> Results=cannot open SCSI device '/dev/pass3' - Permission denied
>>>> 
>>>> 10-Feb 15:18 tape01-sd JobId 256314: 3991 Bad autochanger "loaded? drive
>>>> 0" command: ERR=Child exited with code 1.
>>>> Results=cannot open SCSI device '/dev/pass3' - Permission denied
>>>> 
>>>> 10-Feb 15:18 tape01-sd JobId 256314: 3991 Bad autochanger "loaded? drive
>>>> 0" command: ERR=Child exited with code 1.
>>>> Results=cannot open SCSI device '/dev/pass3' - Permission denied
>>>> 
>>>> 10-Feb 15:18 tape01-sd JobId 256314: 3991 Bad autochanger "loaded? drive
>>>> 0" command: ERR=Child exited with code 1.
>>>> Results=cannot open SCSI device '/dev/pass3' - Permission denied
>>>> 
>>>> 10-Feb 15:18 tape01-sd JobId 256314: 3304 Issuing autochanger "load slot
>>>> 10, drive 0" command for vol 000013L4.
>>>> 10-Feb 15:18 tape01-sd JobId 256314: Fatal error: 3992 Bad autochanger
>>>> "load slot 10, drive 0": ERR=Child exited with code 1.
>>>> Results=cannot open SCSI device '/dev/pass3' - Permission denied
>>>> ###
>>>> 
>>>> --
>>>> Dan Langille - BSDCan / PGCon
>>>> dan AT langille DOT org <mailto:dan AT langille DOT org> <mailto:dan AT 
>>>> langille DOT org>


> On 02/10/2017 06:14 PM, Dan Langille wrote:
>>> On Feb 10, 2017, at 11:24 AM, Mike Fröhner <mikefroehner AT gmx DOT de
>>> <mailto:mikefroehner AT gmx DOT de>> wrote:
>>> 
>>> How do you client config look like for crey-fd? It must be something like:
>>> 
>>> Client {
>>>  Name = crey-fd
>>>  Address = <hostname>
>>>  ...
>>> }
>>> 
>>> If you specify a hostname for Address this hostname must be resolvable.
>> 
>> Yes:
>> 
>> Client {
>>  Name           = crey-fd
>>  Address        = crey.int.unixathome.org <http://crey.int.unixathome.org>
>> 
>> 
>>> Did you check this?
>> 
>> Yes, that works:
>> 
>> $ dig +short crey.int.unixathome.org <http://crey.int.unixathome.org>
>> 10.55.0.10
>> $ dig +short -x 10.55.0.10
>> crey.int.unixathome.org <http://crey.int.unixathome.org>.
>> $

> On Feb 10, 2017, at 12:18 PM, Mike Fröhner <mikefroehner AT gmx DOT de> wrote:
> 
> If bacula-dir and -sd run on different hosts: Did you also verify this 
> works on the bacula-sd host and not just on the bacula-dir host.

They are on different host.  The checks were run on four hosts:

- bacula-dir host
- bacula-sd hosts (both read and write)
- a fourth host unrelated to the backup

-- 
Dan Langille - BSDCan / PGCon
dan AT langille DOT org




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users