From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: git clone fails with error chmod on config.lock failed: Invalid argument
Date: Wed, 20 Apr 2016 14:29:00 -0000 [thread overview]
Message-ID: <20160420142545.GB25668@calimero.vinschen.de> (raw)
In-Reply-To: <57177EB4.6050902@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1862 bytes --]
On Apr 20 15:05, Tomas Jura wrote:
> On 04/19/2016 03:39 PM, Corinna Vinschen wrote:
> >>BTW: My machine is Windows Server 2008, yesterday I also run the Windows
> >>update procedure before I notified the chmod error.
> >>A months ago, I had to migrate to the new AD account. The cygwin was
> >>installed using my old account, which is deleted now. Is it possible that
> >>the query to AD runs under my old account?
> >That's a good question. The problem is that I can't see *why* the
> >requests fail. This bugs me since failing LookupAccountSid calls should
> >result in a debug message when running strace.
> >
> >Do you have changed your /etc/nsswitch.conf file by any chance?
> No I did not. All lines are commented out there.
>
> >
> >Would you mind to create strace output of the command `id'?
> See attachment
Thanks. It's not helpful, unfortunately. The only hint that something
is going wrong is the same message as with chmod:
internal_getlogin: group not found in group DB
There's no other strace message even remotely related to account mapping.
I don't grok that. There should really be some error message :(
Btw., what's the output of `id'?
I'm wondering... is it possible that LDAP access to your DCs is
restricted?
Also, can you change /etc/nsswitch.conf like this:
db_enum: cache local primary
(see https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-mapping-nsswitch-enum)
exit and restart your shell and call `getent group'? What does it
print? Are the AD accounts enumerated and what info is printed for
them? Examples are sufficent, I don't need your entire AD DB :)
Also, what does `getent passwd $USER' print?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-20 14:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 16:34 git clone fails with: error: " Rainer Blome
2016-01-27 18:33 ` Ken Brown
2016-01-27 18:39 ` Corinna Vinschen
2016-01-28 6:35 ` Christopher Cobb
2016-01-28 14:31 ` Corinna Vinschen
2016-01-28 15:52 ` chmod failed: Invalid argument [was: git clone fails with: error: chmod on config.lock failed: Invalid argument] Corinna Vinschen
2016-01-28 16:06 ` git clone fails with: error: chmod on config.lock failed: Invalid argument Corinna Vinschen
2016-01-28 17:23 ` Aw: " Rainer Blome
2016-01-28 18:56 ` Corinna Vinschen
2016-04-19 7:22 ` git clone fails with error " Tomas Jura
2016-04-19 7:57 ` Tomas Jura
2016-04-19 8:11 ` Corinna Vinschen
2016-04-19 13:30 ` Tomas Jura
2016-04-19 14:04 ` Corinna Vinschen
2016-04-20 14:06 ` Tomas Jura
2016-04-20 14:29 ` Corinna Vinschen [this message]
2016-04-21 7:29 ` Tomas Jura
2016-04-21 7:49 ` Corinna Vinschen
2016-01-28 14:33 ` git clone fails with: error: " Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160420142545.GB25668@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).