This is the mail archive of the
mailing list for the Cygwin project.
Re: sshd: PID xxxx: fatal: initgroups: myid: Invalid argument.
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 24 Sep 2007 18:16:15 -0400
- Subject: Re: sshd: PID xxxx: fatal: initgroups: myid: Invalid argument.
- References: <email@example.com>
- Reply-to: cygwin at cygwin dot com
Tim Largy wrote:
On a Windows XP machine I am able to run sshd but can't log on to my
local machine (I haven't tried a remote log on):
$ ssh -1 -i .ssh/my_private_key myid@localhost
Connection closed by 127.0.0.1
In order to view sshd debugging information, I've been running the
daemon from the command line via "net start sshd '-d'" and after the
You may want to try this again by running a system-owned shell (take a
look in the email archives for a recipe of how to make one of these).
You can then run 'sshd' with debugging flags right at the command
line and see all the debug output there.
failed ssh login I see the following message in the Windows Event
sshd: PID xxxx: fatal: initgroups: myid: Invalid argument."
where xxxx is the process ID. I've followed the standard Cygwin
instructions on setting up sshd using ssh-host-config followed by
ssh-user-config for myid. This machine is part of a domain, and I have
a fully-populated /etc/passwd and /etc/group files. Any ideas?
Redacted (anonymized) cygcheck -svr output is attached.
Sure looks to me by the message above that your "myid" isn't in
'/etc/groups'. Did you check that?
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html