Some error messages leave a bit to be desired #830

New Issue

Closed

opened 2024-02-16 09:12:45 +00:00 by he32 · 2 comments

he32 commented 2024-02-16 09:12:45 +00:00

Copy Link

What I'm trying to do and why

I'm doing backup of a few hosts with "largish" (more than 500GB) amounts of data to back up.

This is "initial backup sessions", started with

borgmatic --verbosity 1 --syslog-verbosity -1 --list --stats

Some of these backup sessions terminate with an error message which is "less than readable" and which are also "less than concise" in terms of revealing the actual underlying root cause of the error, in that the textual representation of the Unix errno value which gave rise to the error is nowhere to be found in the error message.

Steps to reproduce

I don't know what is actually causing this issue, since the Unix errno value is not revealed. In this concrete example, the error message was emitted after about 178GB of data had been transferred to the repository.

Now, as I understand it, checkpointing at the server end will ensure that "all is not lost", and a re-run will not have to start from scratch, so that's something, at least...

Actual behavior

See the uploaded file. The error message is in essence

/etc/borgmatic/config.yaml: An error occurred

and

Exception: FD exception occurred

which is ... less helpful than it could be in revealing the actual underlying problem.

Expected behavior

The actual underlying errno value ought to be revealed in the error message, instead of an application-specific exception value and an applicaiton-specific stack traceback.

Other notes / implementation ideas

(nothing here above what's stated above)

borgmatic version

1.8.5

borgmatic installation method

Via pkgsrc, pkgin in py310-borgmatic.

Borg version

borg 1.2.6

Python version

3.10 (python310-3.10.13nb4)

Database version (if applicable)

N/A

Operating system and version

NetBSD/amd64 9.3

### What I'm trying to do and why I'm doing backup of a few hosts with "largish" (more than 500GB) amounts of data to back up. This is "initial backup sessions", started with ``` borgmatic --verbosity 1 --syslog-verbosity -1 --list --stats ``` Some of these backup sessions terminate with an error message which is "less than readable" and which are also "less than concise" in terms of revealing the actual underlying root cause of the error, in that the textual representation of the Unix `errno` value which gave rise to the error is nowhere to be found in the error message. ### Steps to reproduce I don't know what is actually causing this issue, since the Unix errno value is not revealed. In this concrete example, the error message was emitted after about 178GB of data had been transferred to the repository. Now, as I understand it, checkpointing at the server end will ensure that "all is not lost", and a re-run will not have to start from scratch, so that's something, at least... ### Actual behavior See the uploaded file. The error message is in essence ``` /etc/borgmatic/config.yaml: An error occurred ``` and ``` Exception: FD exception occurred ``` which is ... less helpful than it could be in revealing the actual underlying problem. ### Expected behavior The actual underlying `errno` value ought to be revealed in the error message, instead of an application-specific exception value and an applicaiton-specific stack traceback. ### Other notes / implementation ideas (nothing here above what's stated above) ### borgmatic version 1.8.5 ### borgmatic installation method Via pkgsrc, `pkgin in py310-borgmatic`. ### Borg version borg 1.2.6 ### Python version 3.10 (python310-3.10.13nb4) ### Database version (if applicable) N/A ### Operating system and version NetBSD/amd64 9.3

err.txt

5.6 KiB

witten commented 2024-02-16 17:18:34 +00:00

Owner

Copy Link

This looks like an internal Borg error, so you might consider filing a ticket with the Borg project after checking the existing issues.

In terms of borgmatic's handling of this Borg error, it does show Borg's errno in the form of ... returned non-zero exit status 2, but that's just Borg's generic exit code and has nothing to do with the specific FD exception.

Note that Borg 1.4 does make more specific error codes available to borgmatic, but Borg 1.4 hasn't had a stable release yet.

I hope some of that helps!

This looks like an internal Borg error, so you might consider filing a ticket with [the Borg project](https://github.com/borgbackup/borg/issues) after [checking the existing issues](https://github.com/borgbackup/borg/issues?q=is%3Aissue+%22FD+exception+occurred%22+). In terms of borgmatic's handling of this Borg error, it does show Borg's `errno` in the form of `... returned non-zero exit status 2`, but that's just Borg's generic exit code and has nothing to do with the specific FD exception. Note that Borg 1.4 does make more specific error codes available to borgmatic, but Borg 1.4 hasn't had a stable release yet. I hope some of that helps!

witten added the

question / support

label 2024-02-16 17:18:41 +00:00

witten commented 2024-02-26 17:10:20 +00:00

Owner

Copy Link

Closing for now, but please let me know if you have any other feedback on this! Thanks.

Closing for now, but please let me know if you have any other feedback on this! Thanks.

witten closed this issue 2024-02-26 17:10:20 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#830

No description provided.