Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 4 subscribers
  • Views 8569 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Postgres Archival Logging generating error after database rebuild to clear log generated disk space

Scott Spangler
Dear Community:
 
I am running a UTM-HA in AWS with a warm standby. I have a 100GB of space dedicated to the primary EC2 UTM Instance. I noticed it was over 90 % full for a reason I don't know as this a very new deployment. Through Sophos community support, I determined that the proper step would be to run the Postgres rebuild script. After the rebuild I am seeing the system messages below. The UTM is functioning properly and generating new pg_xlog files, but I can't fix this issue through trying different tactics. It's looking for a 16MB pg_xlog file that doesn't exist anymore and I want to get rid of this error so I can turn on archival logs to AWS s3 and CloudWatch. I can access the database as well, so any help to get this resolved would be highly appreciated.
 
Thanks,
 
Scott
 
Postgres is stuck in a loop, unless I turn the archival feature off in the configuration file.
 
 
Details:
2017:06:28-00:56:39 tcp-sophos-utm-ha-1 postgres[339]: [3486-1] LOG: archive command failed with exit code 2
2017:06:28-00:56:39 tcp-sophos-utm-ha-1 postgres[339]: [3486-2] DETAIL: The failed archive command was: /usr/local/bin/postgres_cloud_backup store pg_xlog/000000010000000000000012 000000010000000000000012
2017:06:28-00:56:41 tcp-sophos-utm-ha-1 postgres[339]: [3487-1] LOG: archive command failed with exit code 2
2017:06:28-00:56:41 tcp-sophos-utm-ha-1 postgres[339]: [3487-2] DETAIL: The failed archive command was: /usr/local/bin/postgres_cloud_backup store pg_xlog/000000010000000000000012 000000010000000000000012
2017:06:28-00:56:42 tcp-sophos-utm-ha-1 postgres[339]: [3488-1] LOG: archive command failed with exit code 2
2017:06:28-00:56:42 tcp-sophos-utm-ha-1 postgres[339]: [3488-2] DETAIL: The failed archive command was: /usr/local/bin/postgres_cloud_backup store pg_xlog/000000010000000000000012 000000010000000000000012
2017:06:28-00:56:42 tcp-sophos-utm-ha-1 postgres[339]: [3489-1] WARNING: transaction log file "000000010000000000000012" could not be archived: too many failures
2017:06:28-00:57:01 tcp-sophos-utm-ha-1 /usr/sbin/cron[20038]: (root) CMD (/var/awslogs/bin/awslogs-nanny.sh > /dev/null 2>&1)
 
 
 


This thread was automatically locked due to age.
Unfiltered HTML