Does 'switch-wal' need any specific port to be open? (ERROR: The WAL file has not been received)

302 views
Skip to first unread message

Saurabh Nanda

unread,
Dec 1, 2017, 4:45:56 AM12/1/17
to Barman, Backup and Recovery Manager for PostgreSQL
Hi Everyone,

I've been scratching my head to solve the following error, but haven't made much progress:

    $ barman switch-wal --force --archive --archive-timeout 180 pg
    The WAL file 0000000100000059000000FF has been closed on server 'pg'
    Waiting for the WAL file 0000000100000059000000FF from server 'pg' (max: 180 seconds)
    ERROR: The WAL file 0000000100000059000000FF has not been received in 180 seconds

I had earlier configured barman on a throwaway VPS and everything worked fine. But when I tried replicating this on our final EC2 instance, I ran into the issue mentioned above. I have ensure the following (even though I don't remember doing this on the VPS):

* SSH from barman => pg is working
* SSH from pg => barman is working
* All firewall rules on 'pg' have been disabled, temporarily

What could be the issue here?

-- Saurabh.

Saurabh Nanda

unread,
Dec 4, 2017, 1:04:59 AM12/4/17
to Barman, Backup and Recovery Manager for PostgreSQL
Any help would be appreciated here. I"m completely stumped with this one.

Amarnath Gopalan

unread,
Dec 12, 2017, 9:53:39 PM12/12/17
to Barman, Backup and Recovery Manager for PostgreSQL
Did you try without the timeout ? , I don't think there is any specific port to be open for switch-wal . Are you getting wal shipped to incoming folder from pg server ?
Reply all
Reply to author
Forward
0 new messages