--syslog-verbosity setting not doing anything #286

New issue

Closed

opened 2020-01-23 07:41:52 +00:00 by aardbol · 4 comments

aardbol commented 2020-01-23 07:41:52 +00:00

Copy link

As discussed in issue #277, the --syslog-verbosity argument doesn't output anything to the journal.

This question was asked:

Are you perhaps using --log-file as well? Doing so disables syslog logging

The answer to that is no because I'm using the systemd unit as is provided.

As discussed in issue #277, the --syslog-verbosity argument doesn't output anything to the journal. This question was asked: `Are you perhaps using --log-file as well? Doing so disables syslog logging` The answer to that is no because I'm using the systemd unit as is provided.

palto42 commented 2020-01-23 18:11:40 +00:00

Contributor

Copy link

For me syslog works fine (Solus Linux), just with the --syslog-verbosity 1 option. It is wither started as systemd service or with sudo.

I can see the log with journalctl -t borgmatic.

For me syslog works fine (Solus Linux), just with the `--syslog-verbosity 1` option. It is wither started as systemd service or with `sudo`. I can see the log with `journalctl -t borgmatic`.

witten commented 2020-01-23 19:52:38 +00:00

Owner

Copy link

Yeah, I'm still not sure why this might be happening. @aardbol, can I get a look at your borgmatic command-line flags? The full output of a run with --verbosity 2 may be helpful as well.

I'm looking at the logging code, and there are currently three situations I see in which syslog doesn't get logged to:

1. --log-file is given on the command-line.
2. It's being run from an interactive console.
3. Neither /dev/log nor /var/run/syslog exist.

Sounds like we can eliminate number 1. And number 2 as well, based on what you mentioned in witten/borgmatic#277 about running borgmatic from a systemd service. For number 3, can you confirm that /dev/log or /var/run/syslog exist? Thanks!

Yeah, I'm still not sure why this might be happening. @aardbol, can I get a look at your borgmatic command-line flags? The full output of a run with `--verbosity 2` may be helpful as well. I'm looking at the logging code, and there are currently three situations I see in which syslog doesn't get logged to: 1. `--log-file` is given on the command-line. 2. It's being run from an interactive console. 3. Neither `/dev/log` nor `/var/run/syslog` exist. Sounds like we can eliminate number 1. And number 2 as well, based on what you mentioned in https://projects.torsion.org/witten/borgmatic/issues/277 about running borgmatic from a systemd service. For number 3, can you confirm that `/dev/log` or `/var/run/syslog` exist? Thanks!

aardbol commented 2020-01-23 21:19:35 +00:00

Author

Copy link

For some reason it works now. I tried journalctl -t borgmatic and all the logs showed up. Then I tried journalctl -g borgmatic (how I checked it before) and that also displays the logs.

Thanks for your help!

For some reason it works now. I tried `journalctl -t borgmatic` and all the logs showed up. Then I tried `journalctl -g borgmatic` (how I checked it before) and that also displays the logs. Thanks for your help!

aardbol closed this issue 2020-01-23 21:19:35 +00:00

witten commented 2020-01-23 22:18:03 +00:00

Owner

Copy link

Weird! Glad to hear it's working now.

Weird! Glad to hear it's working now.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

parallel-borgmatic

command-hook-steps

2.1.7

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.9.14

1.9.13

1.9.12

1.9.11

1.9.10

1.9.9

1.9.8

1.9.7

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

1.8.11

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   

blocked

  

breaking

  

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No labels

blocked

breaking

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

3 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#286

No description provided.