INTL 3:770/1 3:770/3
REPLYADDR invalid@invalid.invalid
REPLYTO 3:770/3.0 UUCP
MSGID: 1dbe29d7
REPLY: 9e6b2f54
PID: SoupGate-Win32 v1.05
bob prohaska writes:
> That's a good start. The -u ssh arguments seem to produce records
> of ssh server activity but nothing about outgoing client connections.
> In my case the problem is with an outgoing (client) session. The
> journalctl -u ssh command reported no ssh client activity at all.
The client doesn’t normally log to the journal. Run your client with
‘ssh -vvv’ for debug logging from the client . However Theo has already
interpreted the diagnostic; you’re probably not going to get much more
out of it than that.
Server logging seems to be quite thin by default. You could try
increasing the LogLevel in /etc/ssh/sshd_config (see ‘man sshd_config’
for possible values). You’ll need to restart the server for this to take
effect (systemctl restart ssh).
However, empirically, it doesn’t seem to have much to say when a
connection is terminated abnormally, so don’t get your hopes up.
I think Theo is probably right about what’s going on here.
> Is there a list of valid unit names somewhere?
systemctl list-units
--
https://www.greenend.org.uk/rjk/
--- SoupGate-Win32 v1.05
* Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)
SEEN-BY: 10/0 1 15/0 90/1 103/705 105/81 106/201 128/260 129/305 135/225
SEEN-BY: 153/757 7715 218/0 1 601 700 840 870 930 220/70 221/1 6 226/17
SEEN-BY: 226/30 100 227/114 229/110 112 113 200 206 307 317 400 426
SEEN-BY: 229/428 452 470 550 616 664 700 240/1120 266/512 267/800
SEEN-BY: 282/1038 291/111 292/854 301/1 113 812 310/31 320/219 322/757
SEEN-BY: 335/364 341/66 342/200 396/45 460/58 633/280 712/848 770/1
SEEN-BY: 770/3 100 330 340 772/210 220 230 5020/400 1042 5058/104
SEEN-BY: 5075/35
PATH: 770/3 1 218/840 221/6 301/1 218/700 229/426
|
