Logging error: [Errno 90] Message too long #389

New Issue

Closed

opened 2021-02-04 13:59:22 +00:00 by grote · 6 comments

grote commented 2021-02-04 13:59:22 +00:00

Copy Link

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)

hooks:
    before_backup:
        - echo "`date` - Starting backup"
        - /usr/local/bin/mariadb-backup

/usr/local/bin/mariadb-backup

#!/bin/sh
mariabackup --backup &> /dev/null

Actual behavior (if a bug)

Cron sends an error email with a Logging error:

/etc/cron.daily/borgmatic:
--- Logging error ---
Traceback (most recent call last):
  File "/usr/lib/python3.7/logging/handlers.py", line 933, in emit
    self.socket.send(msg)
OSError: [Errno 90] Message too long

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.7/logging/handlers.py", line 937, in emit
    self.socket.send(msg)
OSError: [Errno 90] Message too long
Call stack:
  File "/root/.local/bin/borgmatic", line 10, in <module>
    sys.exit(main())
  File "/root/.local/lib/python3.7/site-packages/borgmatic/commands/borgmatic.py", line 787, in main
    summary_logs = parse_logs + list(collect_configuration_run_summary_logs(configs, arguments))
  File "/root/.local/lib/python3.7/site-packages/borgmatic/commands/borgmatic.py", line 685, in collect_configuration_run_summary_logs
    results = list(run_configuration(config_filename, config, arguments))
  File "/root/.local/lib/python3.7/site-packages/borgmatic/commands/borgmatic.py", line 84, in run_configuration
    global_arguments.dry_run,
  File "/root/.local/lib/python3.7/site-packages/borgmatic/hooks/command.py", line 70, in execute_hook
    shell=True,
  File "/root/.local/lib/python3.7/site-packages/borgmatic/execute.py", line 199, in execute_command
    (process,), (input_file, output_file), output_log_level, borg_local_path=borg_local_path
  File "/root/.local/lib/python3.7/site-packages/borgmatic/execute.py", line 129, in log_outputs
    logger.log(output_log_level, remaining_output)

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

#### 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`) ``` hooks: before_backup: - echo "`date` - Starting backup" - /usr/local/bin/mariadb-backup ``` /usr/local/bin/mariadb-backup ``` #!/bin/sh mariabackup --backup &> /dev/null ``` #### Actual behavior (if a bug) Cron sends an error email with a Logging error: ``` /etc/cron.daily/borgmatic: --- Logging error --- Traceback (most recent call last): File "/usr/lib/python3.7/logging/handlers.py", line 933, in emit self.socket.send(msg) OSError: [Errno 90] Message too long During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.7/logging/handlers.py", line 937, in emit self.socket.send(msg) OSError: [Errno 90] Message too long Call stack: File "/root/.local/bin/borgmatic", line 10, in <module> sys.exit(main()) File "/root/.local/lib/python3.7/site-packages/borgmatic/commands/borgmatic.py", line 787, in main summary_logs = parse_logs + list(collect_configuration_run_summary_logs(configs, arguments)) File "/root/.local/lib/python3.7/site-packages/borgmatic/commands/borgmatic.py", line 685, in collect_configuration_run_summary_logs results = list(run_configuration(config_filename, config, arguments)) File "/root/.local/lib/python3.7/site-packages/borgmatic/commands/borgmatic.py", line 84, in run_configuration global_arguments.dry_run, File "/root/.local/lib/python3.7/site-packages/borgmatic/hooks/command.py", line 70, in execute_hook shell=True, File "/root/.local/lib/python3.7/site-packages/borgmatic/execute.py", line 199, in execute_command (process,), (input_file, output_file), output_log_level, borg_local_path=borg_local_path File "/root/.local/lib/python3.7/site-packages/borgmatic/execute.py", line 129, in log_outputs logger.log(output_log_level, remaining_output) ``` #### 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

witten commented 2021-02-05 16:48:45 +00:00

Owner

Copy Link

Thanks for reporting this! Do you happen to know what you're using for system logs? systemd's journal or rsyslog, perhaps?

Thanks for reporting this! Do you happen to know what you're using for system logs? systemd's journal or rsyslog, perhaps?

witten added the bug label 2021-02-05 16:48:52 +00:00

grote commented 2021-02-05 16:57:28 +00:00

Author

Copy Link

rsyslog.service is running at least.

Do I maybe need to set --syslog-verbosity to -1 as well as a workaround?

`rsyslog.service` is running at least. Do I maybe need to set `--syslog-verbosity` to `-1` as well as a workaround?

witten commented 2021-02-05 18:20:30 +00:00

Owner

Copy Link

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!

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!

grote commented 2021-02-05 20:37:36 +00:00

Author

Copy Link

you can try that as a work-around if you really want no logging at all.

I only want to be informed about errors which as I understand would still be reported, right?

But ultimately borgmatic should probably not send too-long log messages to rsyslog!

I agree. That is why I created this ticket ;)

> you can try that as a work-around if you really want no logging at all. I only want to be informed about errors which as I understand would still be reported, right? > But ultimately borgmatic should probably not send too-long log messages to rsyslog! I agree. That is why I created this ticket ;)

witten commented 2021-02-05 21:05:59 +00:00

Owner

Copy Link

I only want to be informed about errors which as I understand would still be reported, right?

That's correct!

> I only want to be informed about errors which as I understand would still be reported, right? That's correct!

witten referenced this issue from a commit 2021-07-30 16:48:38 +00:00

Fix "message too long" error when logging to rsyslog (#389).

witten commented 2021-07-30 16:50:04 +00:00

Owner

Copy Link

While I don't have a repro for this, I believe this is fixed in master now! Should be part of the next release.

While I don't have a repro for this, I believe this is fixed in master now! Should be part of the next release.

witten closed this issue 2021-07-30 16:50:04 +00:00

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

command-hook-steps

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 Label bug

Milestone

No items

No Milestone

Assignees

Clear assignees

witten

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#389