Re: hostname doesn't resolve to itself

2014-01-06 Thread Charles Curley
On Mon, 6 Jan 2014 21:52:53 +0100 Heiko Schlittermann wrote: > ssl.schlittermann.de.3600IN A 212.80.235.130 > pu.schlittermann.de. 3600IN A 212.80.235.130 > > > I think, nothing is wrong with having two PTR records. Even I know > that ancient software used to have

hostname doesn't resolve to itself

2014-01-06 Thread Heiko Schlittermann
Hello, the backup server refuses the connection: Mon Jan 6 21:39:50 2014: thd-0x14aec00: \ amandad: pu.schlittermann.de doesn't resolve to itself, it resolves to ssl.schlittermann.de The names are not obfuscated, you may try to dig(8) around as well. The connection comes from 212.80.235.1

Re: Transient data-path errors when running amcheck

2014-01-06 Thread Jean-Louis Martineau
Try this patch, chg-robot retry the mtx command if it failed with 'No Sense'. Jean-Louis On 01/06/2014 01:04 PM, Steven Backus wrote: The complete output of mtx is not logged, run it on the command line to get the complete output: /usr/sbin/mtx -f /dev/changer nobarcode status Storage

Re: Transient data-path errors when running amcheck

2014-01-06 Thread Steven Backus
> The complete output of mtx is not logged, run it on the command line to > get the complete output: > /usr/sbin/mtx -f /dev/changer nobarcode status Storage Changer /dev/sg6:1 Drives, 7 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Element 1 Loaded) Storage Element

Re: Transient data-path errors when running amcheck

2014-01-06 Thread Jean-Louis Martineau
Steven, The complete output of mtx is not logged, run it on the command line to get the complete output: /usr/sbin/mtx -f /dev/changer nobarcode status 'it always works the 2nd time', Did it always works the 3rd and 4th time? When is the first time? Jean-Louis On 01/06/2014 12:27 PM, S

Re: Transient data-path errors when running amcheck

2014-01-06 Thread Steven Backus
> Amanda can't fix bug in the scsi hardware/firmware. It's possible there's a scsi bug but since it always works the 2nd time hopefully more of a timing issue. > Post the amtape debug file when it fail. amtape.20140106091626.debug: Mon Jan 6 09:16:26 2014: thd-0xe1ff960: amtape: pid 12109 ruid

Re: amlabel segmentation fault

2014-01-06 Thread Jean-Louis Martineau
Kervin, Looks like there is a bug if libcurl use GNUTLS. Can you try the attached patch? Jean-Louis On 01/05/2014 12:10 PM, Kervin L. Pierre wrote: Hi Jean-Louis, Thanks for the response. Is there a way to rebuild with '-g' for debugging support and to avoid stripping symbols? Would that h