--syslog-verbosity setting not doing anything #286
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#286
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
For me syslog works fine (Solus Linux), just with the
--syslog-verbosity 1
option. It is wither started as systemd service or withsudo
.I can see the log with
journalctl -t borgmatic
.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:
--log-file
is given on the command-line./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!For some reason it works now. I tried
journalctl -t borgmatic
and all the logs showed up. Then I triedjournalctl -g borgmatic
(how I checked it before) and that also displays the logs.Thanks for your help!
Weird! Glad to hear it's working now.