how to cross check the wal log count from primary and standby ?

Dear All,

The below error I have pulled from master database after shutting down the standby database then I tried to shutdown master but I got the FATEL error,

Later after shuttindown the standby service ( postgresql-10.service) then master db is shutdown now.

Someone Let me know how to validate the wal log file count with primary and standby ?

scp: /data/ARCHIVELOG/000000010000001C000000AA: No space left on device

2020-04-26 13:50:26 GMT  LOG:  archive command failed with exit code 1

2020-04-26 13:50:26 GMT  DETAIL:  The failed archive command was: scp pg_wal/000000010000001C000000AA 172.29.7.194:/data/ARCHIVELOG/000000010000001C000000AA

2020-04-26 13:50:26 GMT  WARNING:  archiving write-ahead log file "000000010000001C000000AA" failed too many times, will try again later

2020-04-26 13:53:08 GMT  LOG:  received fast shutdown request

2020-04-26 13:53:08 GMT  LOG:  aborting any active transactions

2020-04-26 13:53:08 GMT  LOG:  worker process: logical replication launcher (PID 6648) exited with exit code 1

2020-04-26 13:53:08 GMT  LOG:  shutting down

2020-04-26 13:54:24 GMT [unknown] [unknown]LOG:  connection received: host=[local]

2020-04-26 13:54:24 GMT postgres postgresFATAL:  the database system is shutting down

2020-04-26 13:54:41 GMT [unknown] [unknown]LOG:  connection received: host=[local]

2020-04-26 13:54:41 GMT postgres postgresFATAL:  the database system is shutting down

packet_write_wait: Connection to 172.29.7.194 port 22: Broken pipe

lost connection

2020-04-26 13:54:56 GMT  LOG:  archive command failed with exit code 1

2020-04-26 13:54:56 GMT  DETAIL:  The failed archive command was: scp pg_wal/000000010000001D0000000A 172.29.7.194:/data/ARCHIVELOG/000000010000001D0000000A

ssh: connect to host 172.29.7.194 port 22: Connection refused

lost connection

2020-04-26 13:54:57 GMT  LOG:  archive command failed with exit code 1

2020-04-26 13:54:57 GMT  DETAIL:  The failed archive command was: scp pg_wal/000000010000001D0000000A 172.29.7.194:/data/ARCHIVELOG/000000010000001D0000000A

ssh: connect to host 172.29.7.194 port 22: Connection refused

lost connection

2020-04-26 13:54:58 GMT  LOG:  archive command failed with exit code 1

2020-04-26 13:54:58 GMT  DETAIL:  The failed archive command was: scp pg_wal/000000010000001D0000000A 172.29.7.194:/data/ARCHIVELOG/000000010000001D0000000A

2020-04-26 13:54:58 GMT  WARNING:  archiving write-ahead log file "000000010000001D0000000A" failed too many times, will try again later

ssh: connect to host 172.29.7.194 port 22: Connection refused

lost connection

2020-04-26 13:54:58 GMT  LOG:  archive command failed with exit code 1

2020-04-26 13:54:58 GMT  DETAIL:  The failed archive command was: scp pg_wal/000000010000001D0000000A 172.29.7.194:/data/ARCHIVELOG/000000010000001D0000000A

ssh: connect to host 172.29.7.194 port 22: Connection refused

lost connection

2020-04-26 13:54:59 GMT  LOG:  archive command failed with exit code 1

2020-04-26 13:54:59 GMT  DETAIL:  The failed archive command was: scp pg_wal/000000010000001D0000000A 172.29.7.194:/data/ARCHIVELOG/000000010000001D0000000A

ssh: connect to host 172.29.7.194 port 22: Connection timed out

lost connection

2020-04-26 13:57:09 GMT  LOG:  archive command failed with exit code 1

2020-04-26 13:57:09 GMT  DETAIL:  The failed archive command was: scp pg_wal/000000010000001D0000000A 172.29.7.194:/data/ARCHIVELOG/000000010000001D0000000A

2020-04-26 13:57:09 GMT  WARNING:  archiving write-ahead log file "000000010000001D0000000A" failed too many times, will try again later

2020-04-26 13:57:10 GMT  LOG:  database system is shut down

[postgres@de284194 log]$

Thanks and Best Wishes

Ashok

+91 81975 99922(WhatsApp)