Re: selfcheck request failed: timeout waiting for ACK (with secondary addr on eth0 only)
Thanks, that did the trick (added bind address)... >Force the listen address in the relevant xinetd.d file. This will do the > trick. -- Luc Lalonde, analyste - Département de génie informatique: Éole polytechnique de Montréal (514) 340-4711 x5049 [EMAIL PROTECTED] - If God intended people to be naked, they would be born that way. -- Oscar Wilde -
Re: selfcheck request failed: timeout waiting for ACK (with secondary addr on eth0 only)
Le vendredi 29 février 2008, Luc Lalonde a écrit : > Hello folks, > > I'm finally upgrading from the Amanda v2.4.x series to v2.5.2p1. My > configuration worked fine with the old v2.4.x series... However, I'm > having some strangeness with the new version... in particular with > clients that have a primary and secondary ipaddr on the same interface > (eth0). Here's an example: > > 2: eth0: mtu 1500 qdisc pfifo_fast qlen 100 > link/ether 00:04:23:e0:65:46 brd ff:ff:ff:ff:ff:ff > inet 192.168.1.23/26 brd 192.168.1.63 scope global eth0 > inet 192.168.1.25/26 brd 192.168.1.63 scope global secondary eth0 > inet6 fe80::204:23ff:fee0:6546/64 scope link >valid_lft forever preferred_lft forever > > When I do an "amcheck" on the primary addr (192.168.1.23) , all is > fine... However, if I do it with the secondary addr (192.168.1.25), I > get this message: > > WARNING: secon-ip: selfcheck request failed: timeout waiting for ACK > > Where, secon-ip is 192.168.1.25. I did a "tcpdump -A -v -v udp port > 10080" and it confirms that the Amanda server is sending a request from > the secondary address, but getting an answer from the primary address... > and it doesn't seem to like it: > > clip ### > 22:58:30.256184 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto > 17, length: 153) amanda-server.909 > secon-ip.amanda: UDP, length 125 > [EMAIL PROTECTED]>.r...'`..?.Amanda 2.5 REQ HANDLE 000- SEQ > 1204141709 > end clip ### > clip further down ### > 23:02:51.877040 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto > 17, length: 119) prim-ip.amanda > amanda-server.577: UDP, length 91 > [EMAIL PROTECTED]@.p.'`.A.c..Amanda 2.5 REP HANDLE 000- SEQ > 1204602504 > end clip ### > > I'd really like to get this to work... I use the secondary address in a > dual-node cluster with Heartbeat-DRBD configuration. The secondary > address is used for failover. > Force the listen address in the relevant xinetd.d file. This will do the trick. -- Francis Galiegue, One2team - [EMAIL PROTECTED] [ATTENTION : CHANGEMENT DE COORDONNÉES !] +33178945552, +33683877875, http://www.one2team.com 40 avenue Raymond Poincaré - 75116 PARIS
selfcheck request failed: timeout waiting for ACK (with secondary addr on eth0 only)
Hello folks, I'm finally upgrading from the Amanda v2.4.x series to v2.5.2p1. My configuration worked fine with the old v2.4.x series... However, I'm having some strangeness with the new version... in particular with clients that have a primary and secondary ipaddr on the same interface (eth0). Here's an example: 2: eth0: mtu 1500 qdisc pfifo_fast qlen 100 link/ether 00:04:23:e0:65:46 brd ff:ff:ff:ff:ff:ff inet 192.168.1.23/26 brd 192.168.1.63 scope global eth0 inet 192.168.1.25/26 brd 192.168.1.63 scope global secondary eth0 inet6 fe80::204:23ff:fee0:6546/64 scope link valid_lft forever preferred_lft forever When I do an "amcheck" on the primary addr (192.168.1.23) , all is fine... However, if I do it with the secondary addr (192.168.1.25), I get this message: WARNING: secon-ip: selfcheck request failed: timeout waiting for ACK Where, secon-ip is 192.168.1.25. I did a "tcpdump -A -v -v udp port 10080" and it confirms that the Amanda server is sending a request from the secondary address, but getting an answer from the primary address... and it doesn't seem to like it: clip ### 22:58:30.256184 IP (tos 0x0, ttl 62, id 0, offset 0, flags [DF], proto 17, length: 153) amanda-server.909 > secon-ip.amanda: UDP, length 125 [EMAIL PROTECTED]>.r...'`..?.Amanda 2.5 REQ HANDLE 000- SEQ 1204141709 end clip ### clip further down ### 23:02:51.877040 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto 17, length: 119) prim-ip.amanda > amanda-server.577: UDP, length 91 [EMAIL PROTECTED]@.p.'`.A.c..Amanda 2.5 REP HANDLE 000- SEQ 1204602504 end clip ### I'd really like to get this to work... I use the secondary address in a dual-node cluster with Heartbeat-DRBD configuration. The secondary address is used for failover. Thanks in advance for your help. Luc Lalonde.
