SIGKILL during 'borg check' #717

New Issue

Closed

opened 2023-06-25 10:40:26 +00:00 by pocal · 6 comments

pocal commented 2023-06-25 10:40:26 +00:00

Copy Link

What I'm trying to do and why

Running my usual nightly backup via Borgmatic

Steps to reproduce (if a bug)

Include (sanitized) borgmatic configuration files if applicable.

Actual behavior (if a bug)

See log file below

Expected behavior (if a bug)

Other notes / implementation ideas

Environment

borgmatic version: [1.7.14]

Use sudo borgmatic --version or sudo pip show borgmatic | grep ^Version

borgmatic installation method: [Fedora dnf]

Borg version: [1.2.4]

Use sudo borg --version

Python version: [3.13.11]

Use python3 --version

Database version (if applicable): [N/A]

Use psql --version or mysql --version on client and server.

operating system and version: [Fedora 38]

#### What I'm trying to do and why Running my usual nightly backup via Borgmatic #### Steps to reproduce (if a bug) Include (sanitized) borgmatic configuration files if applicable. #### Actual behavior (if a bug) See log file below #### Expected behavior (if a bug) #### Other notes / implementation ideas #### Environment **borgmatic version:** [1.7.14] Use `sudo borgmatic --version` or `sudo pip show borgmatic | grep ^Version` **borgmatic installation method:** [Fedora dnf] **Borg version:** [1.2.4] Use `sudo borg --version` **Python version:** [3.13.11] Use `python3 --version` **Database version (if applicable):** [N/A] Use `psql --version` or `mysql --version` on client and server. **operating system and version:** [Fedora 38]

witten commented 2023-06-25 15:41:12 +00:00

Owner

Copy Link

Thanks for filing this. Could I get a look at the log output of borgmatic when you experience this error? Also, can I see your borgmatic configuration file (redacted if necessary)?

It's possible that you're experiencing the issues from #711 or #713, and that upgrading to 1.7.15 will fix this. It's also possible this is an entirely new problem!

Thanks for filing this. Could I get a look at the log output of borgmatic when you experience this error? Also, can I see your borgmatic configuration file (redacted if necessary)? It's possible that you're experiencing the issues from #711 or #713, and that upgrading to 1.7.15 will fix this. It's also possible this is an entirely new problem!

witten added the

waiting for response

label 2023-06-28 18:26:17 +00:00

witten commented 2023-10-28 03:49:45 +00:00

Owner

Copy Link

Closing due to inactivity. But I'd be happy to reopen this if you'd like to revisit. Thanks!

Closing due to inactivity. But I'd be happy to reopen this if you'd like to revisit. Thanks!

witten closed this issue 2023-10-28 03:49:45 +00:00

pocal commented 2023-10-28 11:04:23 +00:00

Author

Copy Link

Closing due to inactivity. But I'd be happy to reopen this if you'd like to revisit. Thanks!

I'd actually forgotten about this. It hasn't happened again recently, thanks.

> Closing due to inactivity. But I'd be happy to reopen this if you'd like to revisit. Thanks! I'd actually forgotten about this. It hasn't happened again recently, thanks.

witten commented 2023-10-28 17:08:11 +00:00

Owner

Copy Link

Uh oh. So could I get a look at the log output of borgmatic when you experience this error? Also, can I see your borgmatic configuration file (redacted if necessary)? Thanks!

Uh oh. So could I get a look at the log output of borgmatic when you experience this error? Also, can I see your borgmatic configuration file (redacted if necessary)? Thanks!

witten reopened this issue 2023-10-28 17:08:11 +00:00

pocal commented 2023-10-28 17:51:55 +00:00

Author

Copy Link

As I said, the error hasn't happened in a long time, so I don't have a record of it. I'll post my config and patterns files in any case.

As I said, the error hasn't happened in a long time, so I don't have a record of it. I'll post my config and patterns files in any case.

witten commented 2023-10-28 20:29:04 +00:00

Owner

Copy Link

Got it, thanks!

Got it, thanks!

witten closed this issue 2023-10-28 22:48:06 +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#717

No description provided.