Logging error: [Errno 90] Message too long #389
Labels
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: borgmatic-collective/borgmatic#389
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?
What I'm trying to do and why
Steps to reproduce (if a bug)
run borgmatic as a daily cronjob in Debian with
--verbosity -1
and use a hook that produces lots of output (even if piped to&> /dev/null
)/usr/local/bin/mariadb-backup
Actual behavior (if a bug)
Cron sends an error email with a Logging error:
Expected behavior (if a bug)
Other notes / implementation ideas
Environment
borgmatic version: 1.5.12
borgmatic installation method: pip
Borg version: borg 1.1.9
Python version: Python 3.7.3
operating system and version: Debian stable
Thanks for reporting this! Do you happen to know what you're using for system logs? systemd's journal or rsyslog, perhaps?
rsyslog.service
is running at least.Do I maybe need to set
--syslog-verbosity
to-1
as well as a workaround?Yes, you can try that as a work-around if you really want no logging at all. But ultimately borgmatic should probably not send too-long log messages to rsyslog!
I only want to be informed about errors which as I understand would still be reported, right?
I agree. That is why I created this ticket ;)
That's correct!
While I don't have a repro for this, I believe this is fixed in master now! Should be part of the next release.