Mailing List Archive: [Bug 3649] Control sockets do not connect anymore (after updating OpenSSH)

https://bugzilla.mindrot.org/show_bug.cgi?id=3649

--- Comment #7 from wolfgang.liessmann@web.de ---
Even if I leave away '-f' the master process forks into background.
A file 'socket.tmp' is created (see below), with both processes running
in the same directory.

Master process:

> $ ssh -vvv -MN -o ControlPersist=20 -S socket.tmp host1
> [...]
> debug1: forking to background
> $

Client process:

> $ ls -l socket.tmp
> srw------- 1 wolf staff 0 18 Jan 01:43 socket.tmp
> $ ssh -vvv -S socket.tmp host1 /some_path/some_script.sh
> [...]
> Control socket connect(socket.tmp): Connection refused
> [We then proceed with manual authentication.]
> [...]

--
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs

https://bugzilla.mindrot.org/show_bug.cgi?id=3649

--- Comment #10 from Damien Miller <djm@mindrot.org> ---
Does the main process disappear when using -f but not ControlPersist?

If so, then we can use that to get logs. Something like:

ssh -oControlPersist=no -nNf -vvv -oControlMaster=yes yourhost

will background the main mux process but it will still write debug logs
to the terminal. Hopefully one of these will shed light on what is
happening here.

--
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
_______________________________________________
openssh-bugs mailing list
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs