verbosity flag producing remote ssh output even at -1 level #552

New Issue

Closed

opened 2022-06-26 20:01:11 +00:00 by xrisk · 2 comments

xrisk commented 2022-06-26 20:01:11 +00:00

Copy Link

root@xxx:~# borgmatic --verbosity -1
Remote: Warning: Permanently added 'xxx,xxx' (ECDSA) to the list of known hosts.
Remote: Warning: Permanently added 'xxx,xxx' (ECDSA) to the list of known hosts.
Remote: /etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot change locale (C.UTF-8)

Expected: remote warnings should not appear.

borg version: 1.2.1
borgmatic version: 1.6.4

FWIW: on a different host running borgmatic 1.5.22, I do not see these remote warnings. I assume this is a regression.

``` root@xxx:~# borgmatic --verbosity -1 Remote: Warning: Permanently added 'xxx,xxx' (ECDSA) to the list of known hosts. Remote: Warning: Permanently added 'xxx,xxx' (ECDSA) to the list of known hosts. Remote: /etc/profile.d/lang.sh: line 19: warning: setlocale: LC_CTYPE: cannot change locale (C.UTF-8) ``` Expected: remote warnings should not appear. borg version: 1.2.1 borgmatic version: 1.6.4 FWIW: on a different host running borgmatic 1.5.22, I do not see these remote warnings. I assume this is a regression.

witten commented 2022-06-27 03:22:44 +00:00

Owner

Copy Link

Thanks for filing this! It's something that sounds totally plausible as a bug, because currently borgmatic does nothing to alter ssh's verbosity. I could imagine adding -o LogLevel=error to ssh_command whenever borgmatic's verbosity is -1 as a way to solve this.

However.. I can't seem to reproduce the problem locally! I'm using the same version of borgmatic as you with Borg 1.2.0, and when I set the following so as not to get an interactive prompt for an unknown host ...

storage:
    ssh_command: ssh -o StrictHostKeyChecking=no

... I do get the Remote: Warning: Permanently added ... message from ssh, but only at the borgmatic verbosity levels 1 and higher. At verbosity levels 0 and -1, the ssh warning is completely suppressed.

So can you tell me a little more about your setup? Do you have the ssh_command option or the BORG_RSH environment variable set? How are you running borgmatic when this behavior occurs? Interactively at the command-line or with cron/systemd? Any other configuration that might be relevant?

Thanks!

Thanks for filing this! It's something that sounds totally plausible as a bug, because currently borgmatic does nothing to alter ssh's verbosity. I could imagine adding `-o LogLevel=error` to `ssh_command` whenever borgmatic's verbosity is `-1` as a way to solve this. However.. I can't seem to reproduce the problem locally! I'm using the same version of borgmatic as you with Borg 1.2.0, and when I set the following so as not to get an interactive prompt for an unknown host ... ``` storage: ssh_command: ssh -o StrictHostKeyChecking=no ``` ... I *do* get the `Remote: Warning: Permanently added ...` message from ssh, but only at the borgmatic verbosity levels `1` and higher. At verbosity levels `0` and `-1`, the ssh warning is completely suppressed. So can you tell me a little more about your setup? Do you have the `ssh_command` option or the `BORG_RSH` environment variable set? How are you running borgmatic when this behavior occurs? Interactively at the command-line or with cron/systemd? Any other configuration that might be relevant? Thanks!

witten commented 2023-02-04 17:19:22 +00:00

Owner

Copy Link

Closing now due to inactivity / lack of repro, but I'd be happy to reopen if you've got more details. Thanks!

Closing now due to inactivity / lack of repro, but I'd be happy to reopen if you've got more details. Thanks!

witten closed this issue 2023-02-04 17:19:27 +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#552

No description provided.