Trying to back up postgresql causes 'timeout waiting for ACK' errors

[nick]

Hi all,

I've just upgraded amanda from 2.6 to 3.2, in order to get backups of my postgresql (9.0) databases.

I followed the instructions here: [url]http://wiki.zmanda.com/index.php/How_To:Use_Amanda_to_Back_Up_PostgreSQL[/url]

but when I run 'amcheck DailySet1', I get:

Amanda Backup Client Hosts Check
--------------------------------
WARNING: myserver.mydomain.com: selfcheck request failed: timeout waiting for ACK

Is there any easy-ish way to debug ampgsql-related issues?

My config is quite simple (almost exactly matches that wiki page).

thanks in advance!

[paddy]

This is probably Amanda server/client communication problem (not related to postgres)

See [url]http://wiki.zmanda.com/index.php/Planner:_ERROR_Request_to_AMANDA_CLIENT_failed:_ti meout_waiting_for_ACK[/url]
and related links in the section

Paddy

[nick]

This is probably Amanda server/client communication problem (not related to postgres)

See [url]http://wiki.zmanda.com/index.php/Planner:_ERROR_Request_to_AMANDA_CLIENT_failed:_ti meout_waiting_for_ACK[/url]
and related links in the section

Paddy

Hi Paddy, I don't think so. I'm backing up a database which happens to be running on the backup server. I am able to successfully back up files on that machine, too, so I know the basic communication between amanda client/server works, through xinetd. This has to be related to the database piece, but I don't see any diagnostics to help me figure it out... Thanks for the pointer, though!

[nick]

OK, figured out what was going on. The dumptype definition from [url]http://wiki.zmanda.com/index.php/How_To:Use_Amanda_to_Back_Up_PostgreSQL[/url] can't really be used as-is... It would normally need to include global so that it inherits the 'auth bsdtcp' that other dumptypes in the normal config use.

Thanks for the quick response!

[nick]

Now that I've gotten past the xinetd auth issues, I'm stuck at the next step and would love any ideas.

In my backup email, I see that amanda thinks the backup failed because:

FAILED DUMP DETAILS:
 /-- mydbserver.mydomain.com /var/lib/postgresql/9.0/main lev 0 FAILED [NOTICE:  pg_stop_backup complete, all required WAL segments have been archived]

It looks like postgresql was just giving me a message, but amanda treated it as a failure. anyone know how to either suppress that message in postgres, or convince amanda to not think of it as a failure? Thanks again!