cancel
Showing results for 
Search instead for 
Did you mean: 

BART error code 134

Highlighted
Adventurer

BART error code 134

During the daily backup routine, the following error occurred:

 

[2019-09-17 20:10:15] Execução do backup:
NOTICE: pg_stop_backup complete, all required WAL segments have been archived terminate called after throwing an instance of 'std::string'
INFO: DebugTarget - getVar(checkDiskSpace.bytesAvailable)
INFO: new backup identifier generated 1489052137780
INFO: creating 2 harvester threads
[2019-09-17 23:34:20] Erro no backup (RESULT=134).

 

what does this error 134?

5 REPLIES 5
EDB Team Member

Re: BART error code 134

Hi agbdpostgres,

 

The information shared by you is not sufficient to look into your issue.

Could you please share mre details like

The bart backup log
The configuration file.

The configuration seems to be for incremental backup.

Adventurer

Re: BART error code 134

Hi Rahul!

 

File Contents: /usr/edb/bart/etc/bart.cfg :

[BART]

bart_host= postgres@192.168.1.13

backup_path = /backup/bart

pg_basebackup_path = /usr/edb/9.5AS/bin/pg_basebackup

logfile = /tmp/bart21.log

scanner_logfile = /tmp/bart_scanner21.log

thread_count = 5

retention_policy = 2 backups

copy_wals_during_restore = disabled

 

[PGServer]

host = 192.168.1.10

port = 5432

user = postgres

cluster_owner = postgres

description = "PostgreSQL Server"

tablespace_path = 681142146=/postgres/tblspc/data/

xlog_method = stream

remote_host = postgres@192.168.1.10

allow_incremental_backups = enabled

 

The command that is sent:

/usr/edb/bart/bin/bart -d -c /usr/edb/bart/etc/bart.cfg backup -F p -s PostgreServer

 

The script contains the output code file collection:

RESULT="$?"

echo "[$(date +"%Y-%m-%d %H:%M:%S")] Backup Error (RESULT=$RESULT)." >> $LOG

 

The result that appears is:

[2019-09-25 02:22:40] Erro no backup (RESULT=134).

 

In Log, we find the following entries, which ends logging in 3 seconds before the error:

 

50007:2019-09-25 02:17:33 -03  DEBUG: quitting thread :3

50007:2019-09-25 02:18:30 -03  DEBUG: quitting thread :1

50007:2019-09-25 02:18:44 -03  DEBUG: quitting thread :2

50007:2019-09-25 02:19:29 -03  DEBUG: quitting thread :4

50007:2019-09-25 02:19:59 -03  DEBUG: quitting thread :0

50007:2019-09-25 02:19:59 -03  DEBUG: terminating block-copy threads

50007:2019-09-25 02:19:59 -03  DEBUG: terminating block-copy threads

50007:2019-09-25 02:19:59 -03  DEBUG: terminating block-copy threads

50007:2019-09-25 02:19:59 -03  DEBUG: terminating block-copy threads

50007:2019-09-25 02:19:59 -03  DEBUG: terminating block-copy threads

50007:2019-09-25 02:21:07 -03  DEBUG: copying wals cmd: cp /backup/bart/PGServer/archived_wals/000000070000A2760000005A /backup/bart/PGServer/1569366290664/base/pg_wal/

    ------>>>>> 500 lines logging wal file copy

50007:2019-09-25 02:22:37 -03  DEBUG: copying wals cmd: cp /backup/bart/PGServer/archived_wals/000000070000A27800000057 /backup/bart/PGServer/1569366290664/base/pg_wal/

 

After this we found no further evidence. We are investigating other components that may be affecting us, but knowing what exit code 134 means would help us in the analysis.

EDB Team Member

Re: BART error code 134

Hi

 

  Can you also share the details of below

 

  1. ./bart SHOW-SERVERS
  2. ./bart check-config -s PGServer
  3. ./bart BACKUP -s  PGServer or bart -c /usr/edb/bart/etc/bart.cfg show-backups
  4. Bart Version
  5. Can you attach the logs.There is one option of attach where you can do so.
  6. The way archives status at the location and at the backup location

 

 

Can you check this command that you have used.

 

/usr/edb/bart/bin/bart -d -c /usr/edb/bart/etc/bart.cfg backup -F p -s PostgreServer

 

In your configuration you have used [PGServer]

 

We were able to take backup without any error messages by using the command

 

/usr/edb/bart/bin/bart -d -c /usr/edb/bart/etc/bart.cfg backup -F p -s PGServer

Level 2 Adventurer

Re: BART error code 134

Hi.

 

I would like to report a fact that may help identify the problem and supplement some past information.

 

We note that the backup error is always the same and only happens when there are more than 510 wals files to be copied for backup. With the same settings as bart and PostgreSQL, we have successfully backed up several times when there were less than 510 wals files.

 

By enabling debug, the sequence of operations is always the same as below.


# BART version 2.4
/ usr / edb / bart / bin / bart -d -c /usr/edb/bart/etc/bart-11.cfg backup -F p -s $ SERVERNAME_BART

 

Debug: Server: Global, No of Retained Backups 2
INFO: DebugTarget - getVar (checkDiskSpace.bytesAvailable)
Debug: Total Number of Worker Threads 5
DEBUG: starting LSN of current backup 5A000000 (expected WAL 000000070000A2760000005A)
DEBUG: computed start / stop LSN values: 809477 msecs
INFO: new backup identifier generated 1569366290664
DEBUG: created tablespace layout: 4 msecs
DEBUG: created image directories: 24 msecs
DEBUG: Queued Data Directory (except relation files): 433 msecs
INFO: creating 5 harvester threads
DEBUG: file 'pg_subtrans / 4A56' has disappeared - ignoring
DEBUG: quitting thread: 3
DEBUG: quitting thread: 1
DEBUG: quitting thread: 2
DEBUG: quitting thread: 4
DEBUG: quitting thread: 0
DEBUG: terminating block-copy threads
DEBUG: terminating block-copy threads
DEBUG: terminating block-copy threads
DEBUG: terminating block-copy threads
DEBUG: terminating block-copy threads
NOTICE: pg_stop_backup complete, all required WAL segments have been archived
DEBUG: copying wals cmd: cp / backup / bart / linbdpje20 / archived_wals / 000000070000A2760000005A / backup / bart / linbdpje20 / 1569366290664 / base / pg_wal /

 

... follow several wals copy commands, and after 510 wal files, the following error happens:

terminate called after throwing an instance of 'std :: string'

 

We captured the error code thrown from bart execution, which is equal to 134. That is, the command is receiving an ABORT signal.

 

I believe that with this information, it will be possible to better simulate the problem.

EDB Team Member

Re: BART error code 134

Hi agbdpostgres,

 

Glad to have further updates on the specific error that you have been having in the Bart Backup logs.

You have communication in progress through Support Team on this issue.

Further updates will be shared over that channel.