X-Recipient: archive-cygwin@delorie.com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B4BCD3938C0E
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1627989908;
	bh=T+TDZm2Ykc1yku1CfCIpsYR6a9VXcUN/apDFqsB3p4Q=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=fhvP30i9dAkZUjmox8jn4czbM3zn8tl5rTh10vT9s6RkcxhVnOK8qI4gyAPM7NPo5
	 kvKoMQIgWoLe6KCftYSWIJE32R38phPDGRniFFm9YbLS3oU47X/I7qWpCM4/8DokJY
	 SN38Rg4forVwAvACM9JCXAehtzHTiPWfE8ph6LQo=
X-Original-To: cygwin@cygwin.com
Delivered-To: cygwin@cygwin.com
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org F40F0385E454
Date: Tue, 3 Aug 2021 13:24:35 +0200
To: cygwin@cygwin.com
Subject: Re: Unable to start Cygwin64 terminal after password change
Message-ID: <YQknc7ifE4mNthDK@calimero.vinschen.de>
Mail-Followup-To: cygwin@cygwin.com
References: <DM8PR09MB70959D0E3923BE1BE86F7285A5ED9@DM8PR09MB7095.namprd09.prod.outlook.com>
 <YQenbE7ZbwzzcdQM@calimero.vinschen.de>
 <DM8PR09MB70955B8F8E1A180504AE0718A5EF9@DM8PR09MB7095.namprd09.prod.outlook.com>
 <YQgdnllE3OoKkVOm@calimero.vinschen.de>
 <DM8PR09MB7095EEA62C0E5D51C704CAA5A5EF9@DM8PR09MB7095.namprd09.prod.outlook.com>
 <DM8PR09MB7095E8E61444B71762F84138A5EF9@DM8PR09MB7095.namprd09.prod.outlook.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <DM8PR09MB7095E8E61444B71762F84138A5EF9@DM8PR09MB7095.namprd09.prod.outlook.com>
X-Provags-ID: V03:K1:VxSed1Sz8fJwGZ42VVWPZdga4FPNSJbaPYU1rbICC2BP2nfCc6b
 I2mS9GuHHVLVIqv6PGpcp8aMF08rQUuY9mQDe5aiDeT/b/oTZlEbC6x6EE/uXiuZ0wqgFpn
 cbJMmrmsHqi599iPTcdNPu2ZvSyJB0iiqGFNSzaqH319Vfx1k0K7bjTi4to+zrSwOw3zqdQ
 h08fjPjENwti84n+jE7HA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:Qmy8LA0Gbao=:MBBInfE93E9/BeNySO3rdH
 rv0qL/uFrigoA1kwo7VFU/X0Cm1c1R8WZkdfhj4OT7NgdOly17o7RuQ+peYdj2J9w4dqY+NIz
 DSM9xtt985HYC/BerTzbgm+eEKbSw3cxTkUMP/iij9fpJPo49Di0McacIGZh8tci35dS4GXq0
 SmzCg/Faa/E+DKSV6w7TwMxeVUcrLN6JXCxG6+a3CH5rMCe//cwIMZoLnnSsnc8nRI3CT489H
 joiWHvND1fjPCLjBPAk4Ctu6x8v2JPP8GmquAGSmK9O/NezGnlnwP6XxG894a2P/RZI+JKXqt
 ZCJpkcluljqGVw7k1IwmS/ehfLhfIuSqTxRFA2r0aJDNKSnx+7wq/9Wtucij+hjUHRoewYCuN
 nqcZ/m9ON0g98uQ96aRaOepqWDQZjq4CqB4HTbV6ocWirMME6eH36HbpCK/JfiGb+XBEtSDt+
 5CYklmodOReYH1+vbpdxWem3khYCGe4G8nbY8Uo/AdT48PGT/1mCQ9I3+lFIGh/xPGDBjlntO
 IWbuv2IC/e5/V68npOyTCe+eAUk+EIj9pFLIkqr7DQS7GhcxLbK7Yj5g3TGwyY/Hg==
X-Spam-Status: No, score=-100.2 required=5.0 tests=BAYES_00,
 GOOD_FROM_CORINNA_CYGWIN, KAM_DMARC_NONE, KAM_DMARC_STATUS, RCVD_IN_MSPIKE_H2,
 SPF_HELO_NONE, SPF_NEUTRAL,
 TXREP autolearn=ham autolearn_force=no version=3.4.4
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
 server2.sourceware.org
X-BeenThere: cygwin@cygwin.com
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-request@cygwin.com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request@cygwin.com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin@cygwin.com>
Reply-To: cygwin@cygwin.com
Cc: Corinna Vinschen <corinna-cygwin@cygwin.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces+archive-cygwin=delorie.com@cygwin.com
Sender: "Cygwin" <cygwin-bounces+archive-cygwin=delorie.com@cygwin.com>

On Aug  2 18:31, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> > I'll follow up once I have the output you've requested.
> 
> Well, my Systems people stopped cygserver for me, and I was able to open the "Cygwin64 terminal" without problems...  The machine wasn't rebooted, re-login'ed, nothing.
> 
> So cygserver was the culprit?

Looks like it.  Hard to say what problem it has.  Apart from changing
your password, is it possible that your admins changed some sort of
domain security settings?  Apparently some OS calls fail for cygserver
running under the SYSTEM account.  You should really check with your
admins here first.

If that doesn't give a lead, you'll have to debug cygserver.  Debugging
cygserver to see an error message from the OS calls is a bit tricky.
Start the cygserver service, then start an elevated CMD shell and from
inside the CMD shell:

  tasklist /fi "imagename eq cygserver*"

You the PID in a call to strace:

  strace -p <PID> -o cygserver.out

Next, open a another CMD window, start Cygwin's `id' tool once and then
perform a taskkill on strace.

Hopefully this gives us some hint as to the cause of your problem.


Corinna

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