public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Unable to start Cygwin64 terminal after password change
Date: Tue, 3 Aug 2021 13:24:35 +0200	[thread overview]
Message-ID: <YQknc7ifE4mNthDK@calimero.vinschen.de> (raw)
In-Reply-To: <DM8PR09MB7095E8E61444B71762F84138A5EF9@DM8PR09MB7095.namprd09.prod.outlook.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

  parent reply	other threads:[~2021-08-03 11:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31 21:09 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-07-31 21:46 ` Brian Inglis
2021-08-02  8:06 ` Corinna Vinschen
2021-08-02 15:12   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 16:30     ` Corinna Vinschen
2021-08-02 16:49       ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 18:31         ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 20:58           ` Brian Inglis
2021-08-02 21:38             ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-03  0:38               ` Brian Inglis
2021-08-03  1:47                 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-03 15:23                   ` Brian Inglis
2021-08-03 15:50                     ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-03 17:24                       ` Brian Inglis
2021-08-03 18:12                         ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-03 18:20                           ` john doe
2021-08-04 10:03                         ` Andrey Repin
2021-08-03 11:24           ` Corinna Vinschen [this message]
2021-08-03 15:07             ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 15:16   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-01 16:57 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-01 17:23 ` René Berber
2021-08-01 19:28 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-01 19:53 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 14:59 ` Andrey Repin
2021-08-02 15:14   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 15:20     ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-08-02 21:21       ` Andrey Repin
2021-08-02 21:39         ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]

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=YQknc7ifE4mNthDK@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).