Configure second sshd on the same machine

Configure second sshd on the same machine

[Achim Gratz]

For building 32bit packages I've set up an additional installation on the
same server.  To use it from the outside (like) I'm trying to configure a
second sshd on the server.  So I've installed a cygserver23 and sshd32
service with otherwise identical setup to their 64bit brethren and bumped
the port sshd listens on to 3222.  The services are starting without any
hitch, the port is listening and I can log in via public key or password as
I chose.  The only problem: after sending the command to the new ssh
session, the server closes the connection, claiming that the client had
disconnected.  the client gets an exit code 5.  Does that ring a bell with
anyone?   I can't find any error in the config.  Even when I shut down the
64bit installation completely and let sshd run on the standard port I'm
getting the same result.


Regards,
Achim.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Configure second sshd on the same machine

[Larry Hall (Cygwin)]

On 08/14/2014 12:27 PM, Achim Gratz wrote:
> For building 32bit packages I've set up an additional installation on the
> same server.  To use it from the outside (like) I'm trying to configure a
> second sshd on the server.  So I've installed a cygserver23 and sshd32
> service with otherwise identical setup to their 64bit brethren and bumped
> the port sshd listens on to 3222.  The services are starting without any
> hitch, the port is listening and I can log in via public key or password as
> I chose.  The only problem: after sending the command to the new ssh
> session, the server closes the connection, claiming that the client had
> disconnected.  the client gets an exit code 5.  Does that ring a bell with
> anyone?   I can't find any error in the config.  Even when I shut down the
> 64bit installation completely and let sshd run on the standard port I'm
> getting the same result.

The only time I've seen that is when I start the server in debug mode.


-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Configure second sshd on the same machine

[Achim Gratz]

Larry Hall (Cygwin <reply-to-list-only-lh <at> cygwin.com> writes:
> The only time I've seen that is when I start the server in debug mode.

That's not the problem.  If I create /etc/nologin, I get the message back,
so even that part of the connection works.

But here's one step further: in debug mode I can actually run a single
command.  I can't run a shell since apparently the sshd is unable to locate
a tty. Hmmm....


Regards,
Achim.





--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Configure second sshd on the same machine

[Andrey Repin]

Greetings, Achim Gratz!

>> The only time I've seen that is when I start the server in debug mode.

> That's not the problem.  If I create /etc/nologin, I get the message back,
> so even that part of the connection works.

> But here's one step further: in debug mode I can actually run a single
> command.  I can't run a shell since apparently the sshd is unable to locate
> a tty. Hmmm....

Did you checked the $PATH of a running server? 64- and 32-bit installations
should not cross $PATH's. (It's kinda obvious, but still important enough to
check thoroughly.)


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 14.08.2014, <22:39>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Configure second sshd on the same machine

[Achim Gratz]

Andrey Repin writes:
> Did you checked the $PATH of a running server? 64- and 32-bit installations
> should not cross $PATH's. (It's kinda obvious, but still important enough to
> check thoroughly.)

Yes I did.  That is all correctly set up, the error seems to be a
failure to allocate a tty (in debug mode sshd complains about an
"invalid file descriptor" -- sorry I can't copy the actual error message
since I've gone home for today).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Configure second sshd on the same machine

[Achim Gratz]

Achim Gratz <Stromeko <at> NexGo.DE> writes:
> For building 32bit packages I've set up an additional installation on the
> same server.  To use it from the outside (like) I'm trying to configure a
> second sshd on the server.  So I've installed a cygserver23 and sshd32
> service with otherwise identical setup to their 64bit brethren and bumped
> the port sshd listens on to 3222.

After some back and forth and restarting the services many times I've now
ran into the problem that login in via tcsh on the 64bit sshd would also get
no tty (login via bash and then exec a "tcsh -l" still works).  There is
some interaction going on between the 64bit and 32bit world that I don't
understand, most likely via one of the two service users (cyg_server and
sshd) that have been set up from 64bit.  I've just removed the 32bit
services and rebooted the server due to security updates and the 64bit sshd
reverted back to normal after that.  I can provide an additional service
user for cyg_server32, but for the sshd user I'm stuck with a single account
unless I go and patch the sshd.

If someone has got this working I'd appreciate a short note on exactly how.
 In fact I was planning to have three separate Cygwin installations (a build
environment for 32bit and 64bit plus a 64bit user installation) and three
sshd running on different ports providing remote access to all of them.  The
maddening thing is that it looks like I'm 98% there...


Regards,
Achim.




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple