subject:"Re\: 3.5 amcheck issue"

Re: 3.5 amcheck issue

2017-10-05 Thread Jean-Louis Martineau


Dennis,

Can you also post the amandad debug file from the client esx-201.gbv.de

Jean-Louis

On 05/10/17 11:17 AM, Jean-Louis Martineau wrote:

Dennis,

The debug file is big and hard to follow.
Can you reproduce the issue with just a few host?
  eg. amcheck -c mirror esx-201.gbv.de esx-237.gbv.de
A smaller debug file will help me a lot to understand the issue.

Jean-Louis

On 05/10/17 09:49 AM, Dennis Benndorf wrote:


Attached the zipped debug log.

Dennis


Am 05.10.2017 um 15:18 schrieb Jean-Louis Martineau:

Add
  debug-auth 9
  debug-protocol 9
In amanda.conf.
Retry a new amcheck and the post  the amcheck debug file

Jean-Louis

On 05/10/17 09:07 AM, Dennis Benndorf wrote:


Hi Jean-Louis,

after applying the patch there are much more hosts failing with

*/selfcheck request failed: EOF on read from

/*Regards,
Dennis

Am 05.10.2017 um 14:56 schrieb Dennis Benndorf:


Hi Jean-Louis,

the server has Ubuntu 14.04 installed.

root@SERVER:~/*amanda-3.3.9*# grep GETSERVBYNAME config/config.h
#define HAVE_GETSERVBYNAME 1

root@SERVER:~/*amanda-3.5*# grep GETSERVBYNAME config/config.h
/* #undef HAVE_FUNC_GETSERVBYNAME_R_4 */
/* #undef HAVE_FUNC_GETSERVBYNAME_R_5 */
#define HAVE_FUNC_GETSERVBYNAME_R_6 1
#define HAVE_GETSERVBYNAME 1

I will try the patch.

Regards
Dennis

Am 05.10.2017 um 14:49 schrieb Jean-Louis Martineau:

Dennis,

What OS is your server?
Can you do the following command in the compilation directory?
  grep GETSERVBYNAME config/config.h
  grep GETSERVBYPORT config/config.h

Can you try the attached patch?

Jean-Louis

On 05/10/17 05:30 AM, Dennis Benndorf wrote:


Hi,

we are really excited using amanda-3.5 because of the 
multithread patch. Testing it there seems to be an issue:


If I run

for i in `amadmin mirror hosts`; do echo $i ;amcheck -c 
mirror $i;done


in amanda-3.3.9

  * Two Clients have/'Connection timed out' (bla2,esx-237)
/
  * /One Client has //'No route to host' (dl380-138)
/

The expected result would be that these three hosts are 
mentioned by amcheck in 3.5, but no additional hosts.


Here is what amcheck in 3.5 says:

amanda@dl380-54:~$ amcheck -c mirror
'/usr/local/etc/amanda/mirror/amanda.conf', line 110:
warning: Keyword usetimestamps is deprecated.
Amanda Backup Client Hosts Check

ERROR: gotdb7: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb8: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb9: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: inets1: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: inets2: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb6: selfcheck request failed: EOF on read from gotdb6
ERROR: bla: selfcheck request failed: EOF on read from bla
ERROR: esx-180: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: esx-162: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: sf4200-88: selfcheck request failed: Can't bind a
socket to connect to sf4200-88
ERROR: dl380-138: selfcheck request failed: No route to host
ERROR: bla2: selfcheck request failed: Connection timed out
ERROR: esx-237: selfcheck request failed: Connection timed out
Client check: 244 hosts checked in 568.725 seconds.  13
problems found.
(brought to you by Amanda 3.5)

Do you have an idea why they fail? Do you need additional logs?

Regards,
Dennis 





*Disclaimer*

This message is the property of *CARBONITE, INC.* 
 
and may contain confidential or privileged information.


If this message has been delivered to you by mistake, then do not 
copy or deliver this message to anyone. Instead, destroy it and 
notify me by reply e-mail.










*Disclaimer*

This message is the property of *CARBONITE, INC.* 
 
and may contain confidential or privileged information.


If this message has been delivered to you by mistake, then do not 
copy or deliver this message to anyone. Instead, destroy it and 
notify me by reply e-mail.







This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail

Re: 3.5 amcheck issue

2017-10-05 Thread Jean-Louis Martineau


Dennis,

The debug file is big and hard to follow.
Can you reproduce the issue with just a few host?
  eg. amcheck -c mirror esx-201.gbv.de esx-237.gbv.de
A smaller debug file will help me a lot to understand the issue.

Jean-Louis

On 05/10/17 09:49 AM, Dennis Benndorf wrote:


Attached the zipped debug log.

Dennis


Am 05.10.2017 um 15:18 schrieb Jean-Louis Martineau:

Add
  debug-auth 9
  debug-protocol 9
In amanda.conf.
Retry a new amcheck and the post  the amcheck debug file

Jean-Louis

On 05/10/17 09:07 AM, Dennis Benndorf wrote:


Hi Jean-Louis,

after applying the patch there are much more hosts failing with

*/selfcheck request failed: EOF on read from

/*Regards,
Dennis

Am 05.10.2017 um 14:56 schrieb Dennis Benndorf:


Hi Jean-Louis,

the server has Ubuntu 14.04 installed.

root@SERVER:~/*amanda-3.3.9*# grep GETSERVBYNAME config/config.h
#define HAVE_GETSERVBYNAME 1

root@SERVER:~/*amanda-3.5*# grep GETSERVBYNAME config/config.h
/* #undef HAVE_FUNC_GETSERVBYNAME_R_4 */
/* #undef HAVE_FUNC_GETSERVBYNAME_R_5 */
#define HAVE_FUNC_GETSERVBYNAME_R_6 1
#define HAVE_GETSERVBYNAME 1

I will try the patch.

Regards
Dennis

Am 05.10.2017 um 14:49 schrieb Jean-Louis Martineau:

Dennis,

What OS is your server?
Can you do the following command in the compilation directory?
  grep GETSERVBYNAME config/config.h
  grep GETSERVBYPORT config/config.h

Can you try the attached patch?

Jean-Louis

On 05/10/17 05:30 AM, Dennis Benndorf wrote:


Hi,

we are really excited using amanda-3.5 because of the multithread 
patch. Testing it there seems to be an issue:


If I run

for i in `amadmin mirror hosts`; do echo $i ;amcheck -c 
mirror $i;done


in amanda-3.3.9

  * Two Clients have/'Connection timed out' (bla2,esx-237)
/
  * /One Client has //'No route to host' (dl380-138)
/

The expected result would be that these three hosts are mentioned 
by amcheck in 3.5, but no additional hosts.


Here is what amcheck in 3.5 says:

amanda@dl380-54:~$ amcheck -c mirror
'/usr/local/etc/amanda/mirror/amanda.conf', line 110:
warning: Keyword usetimestamps is deprecated.
Amanda Backup Client Hosts Check

ERROR: gotdb7: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb8: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb9: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: inets1: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: inets2: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb6: selfcheck request failed: EOF on read from gotdb6
ERROR: bla: selfcheck request failed: EOF on read from bla
ERROR: esx-180: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: esx-162: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: sf4200-88: selfcheck request failed: Can't bind a
socket to connect to sf4200-88
ERROR: dl380-138: selfcheck request failed: No route to host
ERROR: bla2: selfcheck request failed: Connection timed out
ERROR: esx-237: selfcheck request failed: Connection timed out
Client check: 244 hosts checked in 568.725 seconds. 13
problems found.
(brought to you by Amanda 3.5)

Do you have an idea why they fail? Do you need additional logs?

Regards,
Dennis 





*Disclaimer*

This message is the property of *CARBONITE, INC.* 
 
and may contain confidential or privileged information.


If this message has been delivered to you by mistake, then do not 
copy or deliver this message to anyone. Instead, destroy it and 
notify me by reply e-mail.










*Disclaimer*

This message is the property of *CARBONITE, INC.* 
 
and may contain confidential or privileged information.


If this message has been delivered to you by mistake, then do not 
copy or deliver this message to anyone. Instead, destroy it and 
notify me by reply e-mail.





This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail

Re: 3.5 amcheck issue

2017-10-05 Thread Jean-Louis Martineau


Add
  debug-auth 9
  debug-protocol 9
In amanda.conf.
Retry a new amcheck and the post  the amcheck debug file

Jean-Louis

On 05/10/17 09:07 AM, Dennis Benndorf wrote:


Hi Jean-Louis,

after applying the patch there are much more hosts failing with

*/selfcheck request failed: EOF on read from

/*Regards,
Dennis

Am 05.10.2017 um 14:56 schrieb Dennis Benndorf:


Hi Jean-Louis,

the server has Ubuntu 14.04 installed.

root@SERVER:~/*amanda-3.3.9*# grep GETSERVBYNAME config/config.h
#define HAVE_GETSERVBYNAME 1

root@SERVER:~/*amanda-3.5*# grep GETSERVBYNAME config/config.h
/* #undef HAVE_FUNC_GETSERVBYNAME_R_4 */
/* #undef HAVE_FUNC_GETSERVBYNAME_R_5 */
#define HAVE_FUNC_GETSERVBYNAME_R_6 1
#define HAVE_GETSERVBYNAME 1

I will try the patch.

Regards
Dennis

Am 05.10.2017 um 14:49 schrieb Jean-Louis Martineau:

Dennis,

What OS is your server?
Can you do the following command in the compilation directory?
  grep GETSERVBYNAME config/config.h
  grep GETSERVBYPORT config/config.h

Can you try the attached patch?

Jean-Louis

On 05/10/17 05:30 AM, Dennis Benndorf wrote:


Hi,

we are really excited using amanda-3.5 because of the multithread 
patch. Testing it there seems to be an issue:


If I run

for i in `amadmin mirror hosts`; do echo $i ;amcheck -c mirror 
$i;done


in amanda-3.3.9

  * Two Clients have/'Connection timed out' (bla2,esx-237)
/
  * /One Client has //'No route to host' (dl380-138)
/

The expected result would be that these three hosts are mentioned 
by amcheck in 3.5, but no additional hosts.


Here is what amcheck in 3.5 says:

amanda@dl380-54:~$ amcheck -c mirror
'/usr/local/etc/amanda/mirror/amanda.conf', line 110: warning:
Keyword usetimestamps is deprecated.
Amanda Backup Client Hosts Check

ERROR: gotdb7: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb8: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb9: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: inets1: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: inets2: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb6: selfcheck request failed: EOF on read from gotdb6
ERROR: bla: selfcheck request failed: EOF on read from bla
ERROR: esx-180: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: esx-162: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: sf4200-88: selfcheck request failed: Can't bind a socket
to connect to sf4200-88
ERROR: dl380-138: selfcheck request failed: No route to host
ERROR: bla2: selfcheck request failed: Connection timed out
ERROR: esx-237: selfcheck request failed: Connection timed out
Client check: 244 hosts checked in 568.725 seconds.  13
problems found.
(brought to you by Amanda 3.5)

Do you have an idea why they fail? Do you need additional logs?

Regards,
Dennis 





*Disclaimer*

This message is the property of *CARBONITE, INC.* 
 
and may contain confidential or privileged information.


If this message has been delivered to you by mistake, then do not 
copy or deliver this message to anyone. Instead, destroy it and 
notify me by reply e-mail.







This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail

Re: 3.5 amcheck issue

2017-10-05 Thread Dennis Benndorf


Hi Jean-Louis,

after applying the patch there are much more hosts failing with

*/    selfcheck request failed: EOF on read from

/*Regards,
Dennis

Am 05.10.2017 um 14:56 schrieb Dennis Benndorf:


Hi Jean-Louis,

the server has Ubuntu 14.04 installed.

root@SERVER:~/*amanda-3.3.9*# grep GETSERVBYNAME config/config.h
#define HAVE_GETSERVBYNAME 1

root@SERVER:~/*amanda-3.5*# grep GETSERVBYNAME config/config.h
/* #undef HAVE_FUNC_GETSERVBYNAME_R_4 */
/* #undef HAVE_FUNC_GETSERVBYNAME_R_5 */
#define HAVE_FUNC_GETSERVBYNAME_R_6 1
#define HAVE_GETSERVBYNAME 1

I will try the patch.

Regards
Dennis

Am 05.10.2017 um 14:49 schrieb Jean-Louis Martineau:

Dennis,

What OS is your server?
Can you do the following command in the compilation directory?
  grep GETSERVBYNAME config/config.h
  grep GETSERVBYPORT config/config.h

Can you try the attached patch?

Jean-Louis

On 05/10/17 05:30 AM, Dennis Benndorf wrote:


Hi,

we are really excited using amanda-3.5 because of the multithread 
patch. Testing it there seems to be an issue:


If I run

    for i in `amadmin mirror hosts`; do echo $i ;amcheck -c mirror 
$i;done


in amanda-3.3.9

  * Two Clients have/'Connection timed out' (bla2,esx-237)
/
  * /One Client has //'No route to host' (dl380-138)
/

The expected result would be that these three hosts are mentioned by 
amcheck in 3.5, but no additional hosts.


Here is what amcheck in 3.5 says:

amanda@dl380-54:~$ amcheck -c mirror
'/usr/local/etc/amanda/mirror/amanda.conf', line 110: warning:
Keyword usetimestamps is deprecated.
Amanda Backup Client Hosts Check

ERROR: gotdb7: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb8: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb9: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: inets1: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: inets2: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: gotdb6: selfcheck request failed: EOF on read from gotdb6
ERROR: bla: selfcheck request failed: EOF on read from bla
ERROR: esx-180: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: esx-162: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: sf4200-88: selfcheck request failed: Can't bind a socket
to connect to sf4200-88
ERROR: dl380-138: selfcheck request failed: No route to host
ERROR: bla2: selfcheck request failed: Connection timed out
ERROR: esx-237: selfcheck request failed: Connection timed out
Client check: 244 hosts checked in 568.725 seconds.  13 problems
found.
(brought to you by Amanda 3.5)

Do you have an idea why they fail? Do you need additional logs?

Regards,
Dennis 





*Disclaimer*

This message is the property of *CARBONITE, INC.* 
 and may contain confidential or privileged 
information.


If this message has been delivered to you by mistake, then do not 
copy or deliver this message to anyone. Instead, destroy it and 
notify me by reply e-mail.

Re: 3.5 amcheck issue

2017-10-05 Thread Dennis Benndorf


Hi Jean-Louis,

the server has Ubuntu 14.04 installed.

root@SERVER:~/*amanda-3.3.9*# grep GETSERVBYNAME config/config.h
#define HAVE_GETSERVBYNAME 1

root@SERVER:~/*amanda-3.5*# grep GETSERVBYNAME config/config.h
/* #undef HAVE_FUNC_GETSERVBYNAME_R_4 */
/* #undef HAVE_FUNC_GETSERVBYNAME_R_5 */
#define HAVE_FUNC_GETSERVBYNAME_R_6 1
#define HAVE_GETSERVBYNAME 1

I will try the patch.

Regards
Dennis

Am 05.10.2017 um 14:49 schrieb Jean-Louis Martineau:

Dennis,

What OS is your server?
Can you do the following command in the compilation directory?
  grep GETSERVBYNAME config/config.h
  grep GETSERVBYPORT config/config.h

Can you try the attached patch?

Jean-Louis

On 05/10/17 05:30 AM, Dennis Benndorf wrote:


Hi,

we are really excited using amanda-3.5 because of the multithread 
patch. Testing it there seems to be an issue:


If I run

    for i in `amadmin mirror hosts`; do echo $i ;amcheck -c mirror 
$i;done


in amanda-3.3.9

  * Two Clients have/'Connection timed out' (bla2,esx-237)
/
  * /One Client has //'No route to host' (dl380-138)
/

The expected result would be that these three hosts are mentioned by 
amcheck in 3.5, but no additional hosts.


Here is what amcheck in 3.5 says:

amanda@dl380-54:~$ amcheck -c mirror
'/usr/local/etc/amanda/mirror/amanda.conf', line 110: warning:
Keyword usetimestamps is deprecated.
Amanda Backup Client Hosts Check

ERROR: gotdb7: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: gotdb8: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: gotdb9: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: inets1: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: inets2: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: gotdb6: selfcheck request failed: EOF on read from gotdb6
ERROR: bla: selfcheck request failed: EOF on read from bla
ERROR: esx-180: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: esx-162: selfcheck request failed: error sending REQ:
write error to: Broken pipe
ERROR: sf4200-88: selfcheck request failed: Can't bind a socket
to connect to sf4200-88
ERROR: dl380-138: selfcheck request failed: No route to host
ERROR: bla2: selfcheck request failed: Connection timed out
ERROR: esx-237: selfcheck request failed: Connection timed out
Client check: 244 hosts checked in 568.725 seconds.  13 problems
found.
(brought to you by Amanda 3.5)

Do you have an idea why they fail? Do you need additional logs?

Regards,
Dennis 





*Disclaimer*

This message is the property of *CARBONITE, INC.* 
 and may contain confidential or privileged 
information.


If this message has been delivered to you by mistake, then do not copy 
or deliver this message to anyone. Instead, destroy it and notify me 
by reply e-mail.

Re: 3.5 amcheck issue

2017-10-05 Thread Jean-Louis Martineau


Dennis,

What OS is your server?
Can you do the following command in the compilation directory?
  grep GETSERVBYNAME config/config.h
  grep GETSERVBYPORT config/config.h

Can you try the attached patch?

Jean-Louis

On 05/10/17 05:30 AM, Dennis Benndorf wrote:


Hi,

we are really excited using amanda-3.5 because of the multithread 
patch. Testing it there seems to be an issue:


If I run

for i in `amadmin mirror hosts`; do echo $i ;amcheck -c mirror $i;done

in amanda-3.3.9

  * Two Clients have/'Connection timed out' (bla2,esx-237)
/
  * /One Client has //'No route to host' (dl380-138)
/

The expected result would be that these three hosts are mentioned by 
amcheck in 3.5, but no additional hosts.


Here is what amcheck in 3.5 says:

amanda@dl380-54:~$ amcheck -c mirror
'/usr/local/etc/amanda/mirror/amanda.conf', line 110: warning:
Keyword usetimestamps is deprecated.
Amanda Backup Client Hosts Check

ERROR: gotdb7: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: gotdb8: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: gotdb9: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: inets1: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: inets2: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: gotdb6: selfcheck request failed: EOF on read from gotdb6
ERROR: bla: selfcheck request failed: EOF on read from bla
ERROR: esx-180: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: esx-162: selfcheck request failed: error sending REQ: write
error to: Broken pipe
ERROR: sf4200-88: selfcheck request failed: Can't bind a socket to
connect to sf4200-88
ERROR: dl380-138: selfcheck request failed: No route to host
ERROR: bla2: selfcheck request failed: Connection timed out
ERROR: esx-237: selfcheck request failed: Connection timed out
Client check: 244 hosts checked in 568.725 seconds.  13 problems
found.
(brought to you by Amanda 3.5)

Do you have an idea why they fail? Do you need additional logs?

Regards,
Dennis 

This message is the property of CARBONITE, INC. and may contain confidential or 
privileged information.
If this message has been delivered to you by mistake, then do not copy or 
deliver this message to anyone.  Instead, destroy it and notify me by reply 
e-mail
diff --git a/common-src/protocol.c b/common-src/protocol.c
index 621c6b7..1ab7294 100644
--- a/common-src/protocol.c
+++ b/common-src/protocol.c
@@ -212,7 +212,7 @@ protocol_sendreq(
 get_platform_and_distro(, );
 if (distro != NULL &&
 	!g_str_equal(distro, "mac") &&
-#if defined HAVE_GETSERVBYNAME_R && defined HAVE_GETSERVBYPORT_R
+#if defined HAVE_FUNC_GETSERVBYNAME_R_4 || defined HAVE_FUNC_GETSERVBYNAME_R_5 || defined HAVE_FUNC_GETSERVBYNAME_R_6
 	1 &&
 #else
 	0 &&

Re: 3.5 amcheck issue

Re: 3.5 amcheck issue

Re: 3.5 amcheck issue

Re: 3.5 amcheck issue

Re: 3.5 amcheck issue

Re: 3.5 amcheck issue

6 matches

Site Navigation

Mail list logo

Footer information