Hello, On 21.06.23 11:22, RVP wrote:
On Wed, 21 Jun 2023, RVP wrote:A `Broken pipe' from ssh means the RHS of the pipeline exited prematurely.Is what I said, but, I see that ssh ignores SIGPIPE (network I/O--duh!), so that error message is even odder. Do a `2>log.txt ssh -vvv ...' and post the `log.txt' file when you send the command-line. -RVP
Thanks for your patience.... It took me some hours to get ready for the test. The command that I issues is:
```vhost2$ 2>log.txt ssh user@srv-net -vvv doas /sbin/dump -X -h 0 -b 64 -0auf - /data/119455aa-6ef8-49e0-b71a-9c87e84014cb > /mnt/test.dump
``` The log output at the time of the was: ``` debug2: tcpwinsz: 197420 for connection: 3 debug2: channel 0: window 1933312 sent adjust 163840 debug2: tcpwinsz: 197420 for connection: 3 debug2: channel 0: window 1933312 sent adjust 163840 debug2: tcpwinsz: 197420 for connection: 3 debug2: channel 0: window 1966080 sent adjust 131072 debug3: send packet: type 1 debug1: channel 0: free: client-session, nchannels 1 debug3: channel 0: status: The following connections are open:#0 client-session (t4 r0 i0/0 o0/0 e[write]/0 fd 6/7/8 sock -1 cc -1 io 0x01/0x00)
Connection to srv-net closed by remote host. Transferred: sent 1119040, received 8256466228 bytes, in 374.4 seconds Bytes per second: sent 2988.7, received 22051060.6 debug1: Exit status -1 ```I would like to apologize for being imprecise in the initial wording of the error message. Without the pipe - i.e. with the redirect - I can't currently see a "client_loop send disconnect" message at all, but "Connection to srv-net closed by remote host.". However, the result is the same - the connection was closed remotely.
By the way, until now I assumed that the problem only occurs from Dom0 to DomU. In the meantime, however, I have encountered it at least once with my previously working variant - another physical host on the LAN after DomU. Since all packets going to and from a DomU also pass through Dom0, it is of course conceivable that this is a problem in Dom0. I have also noticed there that the virtual network interfaces of the DomU in question get transmission errors reported:
```
netbsd_netif_rx_bytes{interface="xvif1i0"} 14371724
netbsd_netif_tx_bytes{interface="xvif1i0"} 29567916243
netbsd_netif_errors{interface="xvif1i0"} 26
```
For your reference you can find the full log at:
https://paste.petermann-it.de/?0a1f841ca7c27c63#DTzA3mJMN4fXqGTNVERaWuLJxLTNU1BByhs3DoEn5i9d
Kind regards
Matthias
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature