Re: dump failed: [request failed: No route to host](too)

[Jean-Louis Martineau]

Tom,

It is the system that return the "No route to host" error.
You should check your system log (on server, client, router, firewall, 
nat, ...) for network error.


Jean-Louis

On 12/09/17 06:01 PM, Tom Robinson wrote:

bump

On 11/09/17 12:45, Tom Robinson wrote:
> Hi,
>
> I've recently migrated our backup server from CentOS 5 to CentOS 7. 
I've also upgraded from amanda

> 3.3.7 to 3.4.5
>
> The amcheck works fine and reports no issues. Yet, on backup runs on 
some DLEs I get the error:

>
> dump failed: [request failed: No route to host](too)
>
> It also appears to be random as to which DLEs fail. Sometimes it's 
just one or two on a client.
> Other times it's all DLEs for a client. And, for any particular 
client it can be a different DLE on

> that client each day.
>
> Below is a dumper..debug log from the server. I'm not sure what to 
check for in there. What other

> logs should I check?
>
> Kind regards,
> Tom
>
> Sun Sep 10 20:16:32.115899592 2017: pid 6088: thd-0x257f400: dumper: 
close_producer_shm_ring

> sem_close(sem_write 0x7fbc1588b000
> Sun Sep 10 20:16:32.115911222 2017: pid 6088: thd-0x257f400: dumper: 
am_sem_close 0x7fbc1588b000 0
> Sun Sep 10 20:16:32.115927349 2017: pid 6088: thd-0x257f400: dumper: 
am_sem_close 0x7fbc15889000 0
> Sun Sep 10 20:16:32.115938800 2017: pid 6088: thd-0x257f400: dumper: 
am_sem_close 0x7fbc1588a000 0
> Sun Sep 10 20:16:32.115949293 2017: pid 6088: thd-0x257f400: dumper: 
am_sem_close 0x7fbc15888000 0
> Sun Sep 10 20:16:32.337361676 2017: pid 6088: thd-0x257f400: dumper: 
getcmd: SHM-DUMP 00-00217 34076
> NULL 5 bentley 9efefbff3f Dispatch 
/var/lib/samba/data/public/Dispatch 1

> 2017:9:6:4:6:22 GNUTAR "" "" "" "" "" "" "" 1 "" "" bsdtcp AMANDA /amand
> a_shm_control-6956-0 20 |" bsdtcp\n 
FAST\n
> YES\n YES\n 
AMANDA\n"""
> Sun Sep 10 20:16:32.337507787 2017: pid 6088: thd-0x257f400: dumper: 
Sending header to localhost:34076
> Sun Sep 10 20:16:32.339939372 2017: pid 6088: thd-0x257f400: dumper: 
make_socket opening socket with

> family 10
> Sun Sep 10 20:16:32.339978452 2017: pid 6088: thd-0x257f400: dumper: 
connect_port: Try port 1024:

> available - Success
> Sun Sep 10 20:16:32.340075462 2017: pid 6088: thd-0x257f400: dumper: 
connect_portrange: Connect from

> :::1024 failed: Connection refused
> Sun Sep 10 20:16:32.340101209 2017: pid 6088: thd-0x257f400: dumper: 
connect_portrange: connect to

> ::1:34076 failed: Connection refused
> Sun Sep 10 20:16:32.342383119 2017: pid 6088: thd-0x257f400: dumper: 
make_socket opening socket with

> family 2
> Sun Sep 10 20:16:32.342418634 2017: pid 6088: thd-0x257f400: dumper: 
connect_port: Try port 1024:

> available - Success
> Sun Sep 10 20:16:32.342489613 2017: pid 6088: thd-0x257f400: dumper: 
connected to 127.0.0.1:34076 

> Sun Sep 10 20:16:32.342501059 2017: pid 6088: thd-0x257f400: dumper: 
our side is 0.0.0.0:1024 

> Sun Sep 10 20:16:32.342509347 2017: pid 6088: thd-0x257f400: dumper: 
try_socksize: send buffer size

> is 131072
> Sun Sep 10 20:16:32.342558663 2017: pid 6088: thd-0x257f400: dumper: 
send request:

> 
> SERVICE sendbackup
> OPTIONS 
features=9efefbfff3fffbf70f;maxdumps=5;hostname=bentley;config=daily;

> 
> GNUTAR
> Dispatch
> /var/lib/samba/data/public/Dispatch
> 1
> bsdtcp
> FAST
> YES
> YES
> AMANDA
> 
>
> 
>
> Sun Sep 10 20:16:32.342572947 2017: pid 6088: thd-0x257f400: dumper: 
security_getdriver(name=bsdtcp)

> returns 0x7fbc153e86a0
> Sun Sep 10 20:16:32.342582472 2017: pid 6088: thd-0x257f400: dumper:
> security_handleinit(handle=0x25e2e70, driver=0x7fbc153e86a0 (BSDTCP))
> Sun Sep 10 20:16:32.343623490 2017: pid 6088: thd-0x257f400: dumper:
> security_streaminit(stream=0x283d6e0, driver=0x7fbc153e86a0 (BSDTCP))
> Sun Sep 10 20:16:32.346176806 2017: pid 6088: thd-0x257f400: dumper: 
make_socket opening socket with

> family 2
> Sun Sep 10 20:16:32.346230063 2017: pid 6088: thd-0x257f400: dumper: 
connect_port: Try port 571:

> available - Success
> Sun Sep 10 20:16:32.346247716 2017: pid 6088: thd-0x257f400: dumper: 
connect_portrange: Connect from
> 0.0.0.0:571 
 
failed: Cannot assign requested address
> Sun Sep 10 20:16:32.346261235 2017: pid 6088: thd-0x257f400: dumper: 
connect_portrange: connect to
> 192.168.0.3:10080 
 
failed: Cannot assign requested address
> Sun Sep 10 20:16:32.348492651 2017: pid 6088: thd-0x257f400: dumper: 
make_socket opening socket with

> family 2
> Sun Sep 10 20:16:32.348526207 2017: pid 6088: thd-0x257f400: dumper: 
connect_port: Try port 585:

> available - Success
> Sun Sep 10 20:18:39.587177652 2017: pid 6088: thd-0x257f400: dumper: 
connect_portrange: Connect from
> 0.0.0.0:585 
 
failed: Connection timed out
> Sun Sep 10 20:18:39.587235409 2017: pid 6088: thd-0x257f400: dumper: 
connect_portrange: connect to
> 192.168.0.3:10080 
 
failed: 

Re: client-crc in header (01591e60:14438416) and client-crc in log (38e41ca3:40960) differ

[Jean-Louis Martineau]

On 12/09/17 01:32 PM, Charles Curley wrote:
> On Fri, 8 Sep 2017 09:42:36 -0400
> Jean-Louis Martineau  wrote:
>
> > Which version of amanda are you using?
> >
> > On 09/08/17 05:03 PM, Charles Curley wrote:
> > > Does anyone know what this message from amrecover means? Is it a
> > > problem?
> > >
> > > client-crc in header (01591e60:14438416) and client-crc in log
> > > (38e41ca3:40960) differ
> >
> > They should be identical.
>
> I managed to loose the data that prompted the email. However, I have
> hit the same thing again.
>
> ./samsung.phone/My_Images/0924191916.jpg
> recovery failed: native-crc in header (016f0cc0:15876112) and 
> native-crc in log (37fc5fa5:7552757760) differ
> ./samsung.phone/My_Images/20150725145803.jpg
> recovery failed: client-crc in header (016f0cc0:15876112) and 
> client-crc in log (37fc5fa5:7552757760) differ
> Extracting files using tape drive chg-disk on host backuphost.
header:
NATIVE-CRC=37fc5fa5:7552757760
CLIENT-CRC=37fc5fa5:7552757760
SERVER-CRC=73c995f3:7524723129

log:
dumper: 37fc5fa5:7552757760 37fc5fa5:7552757760
chunker: 73c995f3:7524723129
taper: 37fc5fa5:7552757760 37fc5fa5:7552757760 73c995f3:7524723129

The header and log looks good, it the error message that do not have the 
correct crc.
Can you post the amidxtaped and amrecover debug files

Jean-Louis
>
> Client Amanda version on recovery is 1:3.3.9-5, i386, Debian 9. The
> backup server is running 1:3.4.3-1, amd64, on Debian 8. The client was
> probably running 3.4.3 when it was backed up.
>
> Which leads me to wonder if the version difference is the root of the
> problem.
>
>
> > Can you post the dump header?
>
> Where do I find it?
>
> > Can you post the dumper/chunker/taper entry for the dle from the
> > log.TIMESTAMP.0 file
>
> The taper/dumper/driver file is huge; I will send that to you
> separately rather than clutter up the list.
>
> The chunker:
>
> --
> root@hawk:/var/log/amanda/server/DailySet1# cat 
> chunker.20170908020318.debug
> Fri Sep 08 02:03:18.017036665 2017: pid 23568: thd-0x1fe1200: chunker: 
> pid 23568 ruid 34 euid 34 version 3.4.3: start at Fri Sep 8 02:03:18 2017
> Fri Sep 08 02:03:18.017069350 2017: pid 23568: thd-0x1fe1200: chunker: 
> Arguments: DailySet1 --log-filename 
> /var/lib/amanda/DailySet1/log.20170908000101.0
> Fri Sep 08 02:03:18.017282597 2017: pid 23568: thd-0x1fe1200: chunker: 
> reading config file /etc/amanda/DailySet1/amanda.conf
> Fri Sep 08 02:03:18.018965392 2017: pid 23568: thd-0x1fe1200: chunker: 
> pid 23568 ruid 34 euid 34 version 3.4.3: rename at Fri Sep 8 02:03:18 2017
> Fri Sep 08 02:03:18.019482881 2017: pid 23568: thd-0x1fe1200: chunker: 
> Amanda::Chunker::Scribe preparing to write, max_memory 1048576
> Fri Sep 08 02:03:18.019589576 2017: pid 23568: thd-0x1fe1200: chunker: 
> Starting  -> 
> )>
> Fri Sep 08 02:03:18.019602892 2017: pid 23568: thd-0x1fe1200: chunker: 
> Final linkage:  
> -(DIRECTTCP_LISTEN)->  -(MEM_RING)-> 
> 
> Fri Sep 08 02:03:18.019607312 2017: pid 23568: thd-0x1fe1200: chunker: 
> setup_impl: 7, 9
> Fri Sep 08 02:03:18.019888712 2017: pid 23568: thd-0x1fe1200: chunker: 
> Starting  -> 
> )>
> Fri Sep 08 02:03:18.019900566 2017: pid 23568: thd-0x1fe1200: chunker: 
> Final linkage:  
> -(DIRECTTCP_LISTEN)->  
> -(PUSH_BUFFER_STATIC)-> 
> Fri Sep 08 02:03:18.019904604 2017: pid 23568: thd-0x1fe1200: chunker: 
> setup_impl: 7, 6
> Fri Sep 08 02:03:18.020413909 2017: pid 23568: thd-0x32f28a0: chunker: 
> do_directtcp_accept: 7
> Fri Sep 08 02:03:18.020434394 2017: pid 23568: thd-0x32f28a0: chunker: 
> read_and_push_static
> Fri Sep 08 02:03:21.022058707 2017: pid 23568: thd-0x32f28a0: chunker: 
> sending XMSG_CRC message
> Fri Sep 08 02:03:21.022075635 2017: pid 23568: thd-0x32f28a0: chunker: 
> read_and_push_static CRC: 5db09edf size 32768
> Fri Sep 08 02:03:21.022086984 2017: pid 23568: thd-0x32f28a0: chunker: 
> xfer_queue_message: MSG:  elt= version=0>
> Fri Sep 08 02:03:21.022103830 2017: pid 23568: thd-0x32f28a0: chunker: 
> xfer_queue_message: MSG:  elt= version=0>
> Fri Sep 08 02:03:21.022279637 2017: pid 23568: thd-0x32f2850: chunker: 
> do_directtcp_accept: 6
> Fri Sep 08 02:03:21.022292006 2017: pid 23568: thd-0x32f2850: chunker: 
> read_to_mem_ring
> Fri Sep 08 02:03:21.022466088 2017: pid 23568: thd-0x1fe1200: chunker: 
> got 8 message from 
> Fri Sep 08 02:03:21.022864682 2017: pid 23568: thd-0x32f2800: chunker: 
> Building type FILE