Re: Unable to start Cygwin64 terminal after password change
Greetings, Brian Inglis! > On 2021-08-03 09:50, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: >>> You were "upgrading" your domain account AD data cached by cygserver. >> >> I restarted my PC at some point with "shutdown /r" -- I have no idea how >> cygserver can preserve its caching across this. It's not a "fast restart". > If Fast Startup is enabled, system data could be retained, such as > domain and/or account data, depending on the system components and > drivers involved; it's not well documented: > https://docs.microsoft.com/en-us/windows-hardware/test/weg/delivering-a-great-startup-and-shutdown-experience > "during user-initiated shutdowns, the kernel, drivers, and services are > preserved and restored, not just restarted." Note: This only relevant for shutdown, not restart. -- With best regards, Andrey Repin Wednesday, August 4, 2021 13:00:14 Sorry for my terrible english... -- 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
Re: Unable to start Cygwin64 terminal after password change
On 8/3/2021 8:12 PM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: "during user-initiated shutdowns, the kernel, drivers, and services are preserved and restored, not just restarted." Which was why I specifically used "shutdown /r", which is: /r Full shutdown and restart the computer. We've been advised by our admins that this command does a true and full restart of the system, including all the kernel parts of it. If I'm not mistaking, this command has nothing to do with "fastboot". You may want to check with your AD server admins about this possibility. I decided to restart my computer on Saturday, while the password had been changed Thursday afternoon. Meanwhile I was perfectly able to actually _use_ my new password to unlock that very same Windows host, and login to different hosts (as soon as the new password was set, and before as well as after the reboot of my work PC). So the caching theory is not quite substantiated, IMO. You may want to check with your AD server admins about this possibility. I did! And they said: "no new policies were added and no current policies were changed". I repeat it again: my new password was working everywhere I needed to enter Might be better to reword than to repeat again. -- John Doe -- 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
RE: Unable to start Cygwin64 terminal after password change
> "during user-initiated shutdowns, the kernel, drivers, and services are > preserved and restored, not just restarted." Which was why I specifically used "shutdown /r", which is: /r Full shutdown and restart the computer. We've been advised by our admins that this command does a true and full restart of the system, including all the kernel parts of it. > You may want to check with your AD server admins about this possibility. I decided to restart my computer on Saturday, while the password had been changed Thursday afternoon. Meanwhile I was perfectly able to actually _use_ my new password to unlock that very same Windows host, and login to different hosts (as soon as the new password was set, and before as well as after the reboot of my work PC). So the caching theory is not quite substantiated, IMO. > You may want to check with your AD server admins about this possibility. I did! And they said: "no new policies were added and no current policies were changed". I repeat it again: my new password was working everywhere I needed to enter it to gain access to a system, including this very PC, whose Cygwin Terminal stopped working all of a sudden. If cygserver does cache the AD information, especially kind of information that is known to be volatile, that cache should have a reasonable refresh time, and to be invalidated as stale after the expiration, so it can be re-fetched from the source. Consider DNS as one such working examples. > I would have to make any assumptions that could be spurious Your asking about Cygwin Setup, specifically, appeared to be quite spurious to me, in the light of this issue here. Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
Re: Unable to start Cygwin64 terminal after password change
On 2021-08-03 09:50, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: You were "upgrading" your domain account AD data cached by cygserver. I restarted my PC at some point with "shutdown /r" -- I have no idea how cygserver can preserve its caching across this. It's not a "fast restart". If Fast Startup is enabled, system data could be retained, such as domain and/or account data, depending on the system components and drivers involved; it's not well documented: https://docs.microsoft.com/en-us/windows-hardware/test/weg/delivering-a-great-startup-and-shutdown-experience "during user-initiated shutdowns, the kernel, drivers, and services are preserved and restored, not just restarted." The system restart did not help. It is also possible then that there could be a problem with AD domain account information propagation delays, or retention of registry information, such that cygserver was reloaded with the same outdated data it had on shutdown, if your updated account information had not yet had sufficient time to be persisted to the ADC and propagated back. You may want to check with your AD server admins about this possibility. I'd really appreciate if you could _read_ my messages before replying. It creates a lot of noise on the list for no reason, and it's not being helpful either to me or others. Thank you for being considerate! Your assumption is incorrect, as I carefully reread any message before deciding if a reply could be helpful, and I would have to make any assumptions that could be spurious, recheck the thread contents while replying to avoid making any assumptions, and cross-check what I want to say with information sources. Please consider that we each have different experience that colours how we approach and address issues, which is why diverse project teams are advantageous for best and sometimes quickest responses. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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
RE: Unable to start Cygwin64 terminal after password change
> You were "upgrading" your domain account AD data cached by cygserver. I restarted my PC at some point with "shutdown /r" -- I have no idea how cygserver can preserve its caching across this. It's not a "fast restart". The system restart did not help. I'd really appreciate if you could _read_ my messages before replying. It creates a lot of noise on the list for no reason, and it's not being helpful either to me or others. Thank you for being considerate! Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
Re: Unable to start Cygwin64 terminal after password change
On 2021-08-02 19:47, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: How do you install and upgrade Cygwin and Packages? Why? I wasn't upgrading anything this time. But when I need to upgrade, I create a ticket for admins to stop cygserver, then I update all the files, and then I create a ticket to restart the service. (BTW, Setup won't be able to complete and update cygwin1.dll if anything of Cygwin is still running -- so it's hard to miss.) You were "upgrading" your domain account AD data cached by cygserver. If access to make changes to executables live fails, Cygwin Setup will arrange for the changes to be made when the system next restarts. Everything worked prior to my password change (and that was the _only_ thing that I was changing, not packages). After that I was unable to start Cygwin Terminal (it blinked "This account is currently not available" at me, and closed immediately). I rebooted the machine, to no avail. As Corinna suggested, your system may be set up for "Fast Restart" or whatever it is now labelled, which may play "fast and loose" with the idea of terminating and restarting system, service, and user processes. "cygcheck" was showing broken output for one of my secondary group name. "id" was showing numeric user / group (nothing broken, though). "strace" for "id" showed it consulted cygserver. > When admin stopped cygserver, right away I was able to start the terminal again (without even any need to re-login, let alone to reboot). > It was all described previously in my emails to this list. The thing is that I _need_ cygserver because I use shared memory. So I will have to ask admin to restart, eventually. Cygserver also caches Cygwin process and user account data, including local SAM and *domain* account data (speeds up all AD data accesses), so it is possible that could mess you up. You might want to make your admins aware of possible issues, and any time you or they are going to change any domain data including accounts, passwords, or structure, that could affect or that matter to Cygwin processes on that system, tell each other, so you can stop Cygwin processes and they can stop cygserver, before any changes, and restart cygserver after. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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
RE: Unable to start Cygwin64 terminal after password change
> 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. I am sure nothing was changed at the domain level -- it's a rather big org here, so doing so would have stirred a lot of confusion. People change their passwords all the time, and last Thursday's afternoon was my turn. That's all. But I'll double check with them, to make sure. > Hopefully this gives us some hint as to the cause of your problem. Thanks! I'll follow your instructions, but I guess for that I have to have elevated privs to strace cygserver. I see what I can do here on my work PC about this matter. Meanwhile, I noticed some discrepancies with my user IDs that were reported while I was locked out of my Cygwin terminal (and cygserver running), with that they are reported now, when everything appears to work correctly (and cygserver is stopped). Cygcheck.exe: with cygserver running (note missing closing parentheses for numeric +User and +Group, and some garbage "mote Desktop Users)"): Output from C:\cygwin64\bin\id.exe UID: 1050182(NCBI_NT+User(1606) GID: 1050182 groups=1050182,1049089(NCBI_NT+Group(513) mote Desktop Users) 555(Remote Desktop Users) 545(Users) ... Cygcheck.exe: after cygserver was stopped: Output from C:\Cygwin64\bin\id.exe UID: 1050182(lavr) GID: 1049089(Domain Users) 1049089(Domain Users) 555(Remote Desktop Users) 545(Users) ... NOTE that my primary GID was wrong -- as it was actually my UID, numerically! Standalone id.exe confirms that. With cygserver running the output was: uid=1050182(NCBI_NT+User(1606)) gid=1050182 groups=1050182,1049089(NCBI_NT+Group(513)),555(Remote Desktop Users),... After it was stopped: uid=1050182(lavr) gid=1049089(Domain Users) groups=1049089(Domain Users),555(Remote Desktop Users),... IDK but it seems like cygserver was doing something very wrong to stuff my UID into my GID (cygcheck was also somehow confused to mess the output in that case). Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
Re: Unable to start Cygwin64 terminal after password change
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 -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
RE: Unable to start Cygwin64 terminal after password change
> How do you install and upgrade Cygwin and Packages? Why? I wasn't upgrading anything this time. But when I need to upgrade, I create a ticket for admins to stop cygserver, then I update all the files, and then I create a ticket to restart the service. (BTW, Setup won't be able to complete and update cygwin1.dll if anything of Cygwin is still running -- so it's hard to miss.) Everything worked prior to my password change (and that was the _only_ thing that I was changing, not packages). After that I was unable to start Cygwin Terminal (it blinked "This account is currently not available" at me, and closed immediately). I rebooted the machine, to no avail. "cygcheck" was showing broken output for one of my secondary group name. "id" was showing numeric user / group (nothing broken, though). "strace" for "id" showed it consulted cygserver. When admin stopped cygserver, right away I was able to start the terminal again (without even any need to re-login, let alone to reboot). It was all described previously in my emails to this list. The thing is that I _need_ cygserver because I use shared memory. So I will have to ask admin to restart, eventually. Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
Re: Unable to start Cygwin64 terminal after password change
On 2021-08-02 15:38, Anton Lavrentiev wrote: All Cygwin services need to be shut down prior to running Cygwin Setup Huh? Where Cygwin Setup is coming from? I don't understand what you are talking about. How do you install and upgrade Cygwin and Packages? -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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
RE: Unable to start Cygwin64 terminal after password change
> I asked this in case something like cygserver was running, or that your user > SID had changed in the meantime (f.e. due to domain migration). > That would actually require a proper reboot. No domain migration, just a password change. It was properly rebooted, nonetheless. Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
RE: Unable to start Cygwin64 terminal after password change
> All Cygwin services need to be shut down prior to running Cygwin Setup Huh? Where Cygwin Setup is coming from? I don't understand what you are talking about. Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
Re: Unable to start Cygwin64 terminal after password change
Greetings, Lavrentiev, Anton (NIH/NLM/NCBI) [C]! >> > Did you reboot your system since password change? I mean proper reboot, not >> >> It was properly rebooted with "shutdown /r" >> > But TBH, I did this out of lack of anything else: I don't think a reboot > should be necessary when a password > is changing. Nothing else on the machine was required to reboot it: That's generally true, as at most you'd have to re-login to make network cache update. I asked this in case something like cygserver was running, or that your user SID had changed in the meantime (f.e. due to domain migration). That would actually require a proper reboot. > Outlook just re-asked for the new password > after some time, but everything else kept working except for "Cygwin64 > terminal"... -- With best regards, Andrey Repin Tuesday, August 3, 2021 0:19:18 Sorry for my terrible english... -- 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
Re: Unable to start Cygwin64 terminal after password change
On 2021-08-02 12: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? When I run id now, I get it all correctly, from both that very terminal: $ id uid=1050182(lavr) gid=1049089(Domain Users) groups=1049089(Domain Users),555(Remote Desktop Users),545(Users),559(Performance Log Users),14(REMOTE INTERACTIVE LOGON),4(INTERACTIVE) and also from "bash" that I used to start from "cmd.exe" (when the terminal wouldn't open up): C:\Windows\System32>cd \cygwin64\bin C:\Cygwin64\bin>bash lavr@NCBIPC9135 /usr/bin $ id uid=1050182(lavr) gid=1049089(Domain Users) groups=1049089(Domain Users),555(Remote Desktop Users),545(Users),559(Performance Log Users),14(REMOTE INTERACTIVE LOGON),4(INTERACTIVE),11(Authenticated Users),15(This Organization),4095(CurrentSession)... Also note that my prompt is not showing anything numeric anymore... Any clues? All Cygwin services need to be shut down prior to running Cygwin Setup and they need to be restarted after Cygwin Setup completes successfully. If Cygwin services are running while Cygwin Setup is running, Cygwin components in use can not be updated, and you should get a Restart to update prompt. If you can not control the services, you should not run Setup: it should all be packaged into a script run elevated by those who have control. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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
RE: Unable to start Cygwin64 terminal after password change
> 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? When I run id now, I get it all correctly, from both that very terminal: $ id uid=1050182(lavr) gid=1049089(Domain Users) groups=1049089(Domain Users),555(Remote Desktop Users),545(Users),559(Performance Log Users),14(REMOTE INTERACTIVE LOGON),4(INTERACTIVE) and also from "bash" that I used to start from "cmd.exe" (when the terminal wouldn't open up): C:\Windows\System32>cd \cygwin64\bin C:\Cygwin64\bin>bash lavr@NCBIPC9135 /usr/bin $ id uid=1050182(lavr) gid=1049089(Domain Users) groups=1049089(Domain Users),555(Remote Desktop Users),545(Users),559(Performance Log Users),14(REMOTE INTERACTIVE LOGON),4(INTERACTIVE),11(Authenticated Users),15(This Organization),4095(CurrentSession)... Also note that my prompt is not showing anything numeric anymore... Any clues? Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
RE: Unable to start Cygwin64 terminal after password change
> Oops. Running cygserver is counter-productive in this case. The actual > fetching of user and group data will then occur inside cygserver and > nothing of import will show up in the trace output. Hmmm.. I'll see what I can do (because it's run with admin privs, which I don't have -- have to create a trouble ticket to have it stopped). Nothing else of Cygwin is running on this machine, BTW. I'll follow up once I have the output you've requested. Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
Re: Unable to start Cygwin64 terminal after password change
On Aug 2 15:12, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > id output, unlike when it posted broken in cygcheck's output as noted > previously, seems unbroken, still with numeric user id: > > uid=1050182(NCBI_NT+User(1606)) gid=1050182 > groups=1050182,1049089(NCBI_NT+Group(513)),555(Remote Desktop > XYZ14),545(XYZ14),559(Performance Log XYZ14),14(REMOTE INTERACTIVE > LOGON),4(INTERACTIVE),11(Authenticated XYZ14),15(This > Organization),4095(CurrentSession),66048(LOCAL),1055696(XYZ0),1055814(XYZ1),1059871(XYZ2),1075845(XYZ3),1055694(XYZ4),1058328(XYZ5),1076430(XYZ6),1049837(XYZ7),1054487(XYZ8),1058337(XYZ9),1079855(XYZ10),1073550(XYZ11),1054490(XYZ12),1085362(XYZ13 > XYZ14),1055672(XYZ15),1055702(XYZ16),1053394(XYZ17),1055703(XYZ18),70145(XYZ19 > XYZ20 XYZ21 XYZ22),1083944(XYZ23),401408(XYZ24 XYZ25 XYZ26) > > The corresponding id.strace file (the command was > "C:\Cygwin64\bin>strace -m all -n -o id.strace id > id.out") is below. > > Note that the automated sanitizing replaced "Users" with XYZ14 in > there (as it did in the id output itself), but I could not find any > numeric->group conversions in the strace output. Noticed also that it > was seemingly trying to connect to cygserver, not sure if that was > successful, but cygserver is up and running: > > C:\Cygwin64\bin>cygrunsrv -L > cygserver > > Like I also noted before, I rebooted my machine, so cygserver (if > anything caching) had been restarted afresh after my password change. Oops. Running cygserver is counter-productive in this case. The actual fetching of user and group data will then occur inside cygserver and nothing of import will show up in the trace output. Can you please stop all Cygwin processes, including cygserver, then open a Windows Command Prompt, and run cd C:\cygwin64\bin strace -o id.out id again? Thanks, 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
RE: Unable to start Cygwin64 terminal after password change
> > Did you reboot your system since password change? I mean proper reboot, not > > It was properly rebooted with "shutdown /r" > But TBH, I did this out of lack of anything else: I don't think a reboot should be necessary when a password is changing. Nothing else on the machine was required to reboot it: Outlook just re-asked for the new password after some time, but everything else kept working except for "Cygwin64 terminal"... Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
RE: Unable to start Cygwin64 terminal after password change
> Is NCBI_NT the primary domain of the machine as well? I. e., is the machine > in the same domain as your user account? Yes, AFAIK. Is it the both the primary domain of the host and my account. Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
RE: Unable to start Cygwin64 terminal after password change
> Did you reboot your system since password change? I mean proper reboot, not It was properly rebooted with "shutdown /r" Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
RE: Unable to start Cygwin64 terminal after password change
id output, unlike when it posted broken in cygcheck's output as noted previously, seems unbroken, still with numeric user id: uid=1050182(NCBI_NT+User(1606)) gid=1050182 groups=1050182,1049089(NCBI_NT+Group(513)),555(Remote Desktop XYZ14),545(XYZ14),559(Performance Log XYZ14),14(REMOTE INTERACTIVE LOGON),4(INTERACTIVE),11(Authenticated XYZ14),15(This Organization),4095(CurrentSession),66048(LOCAL),1055696(XYZ0),1055814(XYZ1),1059871(XYZ2),1075845(XYZ3),1055694(XYZ4),1058328(XYZ5),1076430(XYZ6),1049837(XYZ7),1054487(XYZ8),1058337(XYZ9),1079855(XYZ10),1073550(XYZ11),1054490(XYZ12),1085362(XYZ13 XYZ14),1055672(XYZ15),1055702(XYZ16),1053394(XYZ17),1055703(XYZ18),70145(XYZ19 XYZ20 XYZ21 XYZ22),1083944(XYZ23),401408(XYZ24 XYZ25 XYZ26) The corresponding id.strace file (the command was "C:\Cygwin64\bin>strace -m all -n -o id.strace id > id.out") is below. Note that the automated sanitizing replaced "Users" with XYZ14 in there (as it did in the id output itself), but I could not find any numeric->group conversions in the strace output. Noticed also that it was seemingly trying to connect to cygserver, not sure if that was successful, but cygserver is up and running: C:\Cygwin64\bin>cygrunsrv -L cygserver Like I also noted before, I rebooted my machine, so cygserver (if anything caching) had been restarted afresh after my password change. Strace of id: --- Process 18708 created --- Process 18708 loaded C:\Windows\System32\ntdll.dll at 7ffcdf9a --- Process 18708 loaded C:\Windows\System32\kernel32.dll at 7ffcde32 --- Process 18708 loaded C:\Windows\System32\KernelBase.dll at 7ffcdca2 --- Process 18708 thread 4840 created --- Process 18708 thread 6440 created --- Process 18708 loaded C:\Cygwin64\bin\cygintl-8.dll at 0003ebb0 --- Process 18708 loaded C:\Cygwin64\bin\cygwin1.dll at 00018004 --- Process 18708 thread 9408 created --- Process 18708 loaded C:\Cygwin64\bin\cygiconv-2.dll at 0003ebdc 0 0 [main] id (18708) ** 201 201 [main] id (18708) Program name: C:\Cygwin64\bin\id.exe (windows pid 18708) 15321733 [main] id (18708) OS version: Windows NT-10.0 931826 [main] id (18708) ** --- Process 18708 loaded C:\Windows\System32\advapi32.dll at 7ffcdf11 --- Process 18708 loaded C:\Windows\System32\msvcrt.dll at 7ffcde4c --- Process 18708 loaded C:\Windows\System32\sechost.dll at 7ffcde28 --- Process 18708 loaded C:\Windows\System32\rpcrt4.dll at 7ffcdde9 --- Process 18708 loaded C:\Windows\System32\cryptbase.dll at 7ffcdc26 --- Process 18708 loaded C:\Windows\System32\bcryptprimitives.dll at 7ffcdd9c 45426368 [main] id (18708) sigprocmask: 0 = sigprocmask (0, 0x0, 0x180333190) 9137281 [main] id (18708) open_shared: name shared.5, n 5, shared 0x18003 (wanted 0x18003), h 0x104, *m 6 1087389 [main] id (18708) user_heap_info::init: heap base 0x8, heap top 0x8, heap size 0x2000 (536870912) 1397528 [main] id (18708) open_shared: name S-1-5-21-2137354491-1741569864-122644288-1606.1, n 1, shared 0x18002 (wanted 0x18002), h 0x100, *m 6 897617 [main] id (18708) user_info::create: opening user shared for 'S-1-5-21-2137354491-1741569864-122644288-1606' at 0x18002 917708 [main] id (18708) user_info::create: user shared version 0 1417849 [main] id (18708) fhandler_pipe::create: name \\.\pipe\cygwin-e022582115c10879-18708-sigwait, size 11440, mode PIPE_TYPE_MESSAGE 797928 [main] id (18708) fhandler_pipe::create: pipe read handle 0x11C 798007 [main] id (18708) fhandler_pipe::create: CreateFile: name \\.\pipe\cygwin-e022582115c10879-18708-sigwait 978104 [main] id (18708) fhandler_pipe::create: pipe write handle 0x120 898193 [main] id (18708) dll_crt0_0: finished dll_crt0_0 initialization --- Process 18708 thread 9824 created 5448737 [sig] id (18708) wait_sig: entering ReadFile loop, my_readsig 0x11C, my_sendsig 0x120 2358972 [main] id (18708) time: 1627916384 = time(0x0) 1579129 [main] id (18708) normalize_win32_path: C:\Cygwin64 = normalize_win32_path (\??\C:\Cygwin64) 389167 [main] id (18708) normalize_posix_path: src / 339200 [main] id (18708) normalize_posix_path: / = normalize_posix_path (/) 349234 [main] id (18708) mount_info::add_item: \??\C:\Cygwin64[C:\Cygwin64], /[/], 0x30008 439277 [main] id (18708) mount_info::from_fstab: Try to read mounts from \??\C:\Cygwin64\etc\fstab 1849461 [main] id (18708) normalize_win32_path: C:\Cygwin64\bin = normalize_win32_path (C:\Cygwin64\bin) 349495 [main] id (18708) normalize_posix_path: src /usr/bin 369531 [main] id (18708) normalize_posix_path: /usr/bin = normalize_posix_path (/usr/bin) 339564 [main] id (18708) mount_info::add_item:
Re: Unable to start Cygwin64 terminal after password change
Greetings, Lavrentiev, Anton (NIH/NLM/NCBI) [C]! > I vaguely remember having the same issue some time ago (but then my work PC > was frequently bugchecking > because of a faulty memory module), and I did not tie any recent password > change (if there was any at all) > with my unability to run Cygwin terminal... That time I had to clean my > registry settings pertaining > to Cygwin and then I got the terminal working back (still have a history of > doing so in the support > ticket created back than). I haven't done so just yet. Maybe some other > thing is also in the play here, > and I will gladly provide any necessary information while it persistently and > reproducibly not working, > to have it fixed (rather than crudely worked around). Did you reboot your system since password change? I mean proper reboot, not shutdown then boot up, as that could be faked into hibernation unless specifically configured to avoid. -- With best regards, Andrey Repin Monday, August 2, 2021 17:58:13 Sorry for my terrible english... -- 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
Re: Unable to start Cygwin64 terminal after password change
On Jul 31 21:09, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: > Hi all, > > I seem to be unable to start "Cygwin64 Terminal" (using the standard icon > placed on the desktop when Cygwin gets installed) > after I had to change my password (at work). My account did not change. > What I see is that the terminal window pops up > momentarily with a text "This account is currently not available", and then > closes right away. I'm using my work PC > perfectly fine, and my new password works just as well (using it every time > to log in the system), only the Cygwin terminal > stopped working after the change. I "own" the Cygwin installation on my work > PC (it's installed by me from under my > username). > > Even rebooting the PC did not help to clear this up. > > Weirdly enough, I can start bash from cmd.exe, but then it shows my username > numerically: > > C:\WINDOWS\system32>c:\cygwin64\bin\bash.exe > > NCBI_NT+User(1606)@NCBIPC9135 /cygdrive/c/WINDOWS/system32 > $ uname -a > CYGWIN_NT-10.0 NCBIPC9135 3.2.0(0.340/5/3) 2021-03-29 08:42 x86_64 Cygwin > > Any suggestions? This sounds like LookupAccountSid fails for some reason. Is NCBI_NT the primary domain of the machine as well? I. e., is the machine in the same domain as your user account? If yes, it's very strange that this should occur. If you're in another domain, it might be a problem with domain trusts, but that's just idle musing without knowing what happens under the hood. Please start a CMD shell, cd into your Cygwin bin dir and run strace -o id.out id You might want to check the id.out file for sensitive information (typically environment variables) and you can change group names in id.out as well as in the id output to hide private info, but the info should be complete and make sense (i .e, if you change a group name to XYZ in the id output, change it to XYZ in id.out as well). Please paste the output of id and attach the id.out file to your reply. Thanks, 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
RE: Unable to start Cygwin64 terminal after password change
More info:
Running "cygcheck -rvs" from under bash (that I could only start from cmd.exe
as shown earlier)
does not seem to show anything unusual (I have only single install of Cygwin,
there's no conflict
of any kind, and all the packages check out Okay).
SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS
PWD = '/cygdrive/c/WINDOWS/system32'
HOME = '/'
CYGWIN = 'nodosfilewarning '
...
HKEY_CURRENT_USER\Software\Cygwin
HKEY_CURRENT_USER\Software\Cygwin\Installations
(default) = '\??\C:\Cygwin64'
HKEY_CURRENT_USER\Software\Cygwin\setup
(default) = 'C:\Cygwin64'
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygwin\Installations
(default) = '\??\C:\Cygwin64'
obcaseinsensitive set to 1
Cygwin installations found in the registry:
System: Key: e022582115c10879 Path: C:\Cygwin64
User: Key: e022582115c10879 Path: C:\Cygwin64
c: hd NTFS486939Mb 47% CP CS UN PA FCQU Local Disk
d: cd N/AN/A
s: net NTFS 2789212Mb 79% CP CS UN PA [redacted]
u: net NTFS 20480Mb 82% CP CS UN PA lavr
x: net NTFS 2789212Mb 79% CP CS UN PA [redacted]
y: net NTFS116779Mb 60% CP CS UN PA QU lavr
z: net NTFS116779Mb 60% CP CS UN PA QU home
C:\cygwin64 / system binary,auto
C:\cygwin64\bin /usr/bin system binary,auto
C:\cygwin64\lib /usr/lib system binary,auto
cygdrive prefix /cygdrive userbinary,posix=0,auto
The only thing in that output that still does not seem right is this section
(which I can't show in its entirety, so I am redacting it):
Output from C:\cygwin64\bin\id.exe
UID: 1050182(NCBI_NT+User(1606)
GID: 1050182 groups=1050182,1049089(NCBI_NT+Group(513)
mote Desktop Users)
555(Remote Desktop Users)
545(Users)
...
Note that my username is still numeric and the second line shows some incomplete
group name that has been cut off in the middle ("mote Desktop Users")...
All other (about 20) groups that follow [...] have their numeric and textual
information correct, without any issues...
I vaguely remember having the same issue some time ago (but then my work PC was
frequently bugchecking
because of a faulty memory module), and I did not tie any recent password
change (if there was any at all)
with my unability to run Cygwin terminal... That time I had to clean my
registry settings pertaining
to Cygwin and then I got the terminal working back (still have a history of
doing so in the support
ticket created back than). I haven't done so just yet. Maybe some other thing
is also in the play here,
and I will gladly provide any necessary information while it persistently and
reproducibly not working,
to have it fixed (rather than crudely worked around).
Thanks for looking into this.
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
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
RE: Unable to start Cygwin64 terminal after password change
> Unless of course you execute bash with -noprofile. The only way I can start bash now, is from cmd.exe, since terminal (mintty) is not working for me, as I explained in my first message: C:\WINDOWS\system32>c:\cygwin64\bin\bash NCBI_NT+User(1606)@NCBIPC9135 /cygdrive/c/WINDOWS/system32 $ id -un NCBI_NT+User(1606) I suppose it should have printed something like "NCBI_NT+lavr", but I truly don't remember what it exactly was it showing before. Certainly, though, no numeric part. I used my real and proper username instead of $USER, in all the commands that I was asked to run and show the output. Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
Re: Unable to start Cygwin64 terminal after password change
On 8/1/2021 11:57 AM, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: [snip] BTW, $USER is not defined in the bash environment (not sure if it should be) Quoting man bash: "When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first reads and executes commands from the file /etc/profile, if that file exists." and /etc/profile has a line with: USER="$(/usr/bin/id -un)" then... export ... USER ... Unless of course you execute bash with -noprofile. My account is a domain account here. And everything worked before I had to change my password. Maybe `id -un` does change in this case. -- R. Berber -- 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
RE: Unable to start Cygwin64 terminal after password change
> $ head /proc/version
It seems to be not much different from the 'uname -a' output I showed earlier,
but here it goes:
$ head /proc/version
CYGWIN_NT-10.0-18363 version 3.2.0-340.x86_64 (corinna@calimero) (gcc version
9.3.0 20200312 (Fedora Cygwin 9.3.0-1) (GCC) ) 2021-03-29 08:42 UTC
> getent passwd $USER
NCBI_NT+User(1606)@NCBIPC9135 /cygdrive/c/WINDOWS/system32
$ getent passwd lavr
lavr:*:1050182:1049089:U-NCBI_NT\lavr,S-1-5-21-2137354491-1741569864-122644288-1606:/home/lavr:/bin/bash
There's no stray /etc/passwd that might have gotten in the way, either:
$ cat /etc/passwd
cat: /etc/passwd: No such file or directory
BTW, $USER is not defined in the bash environment (not sure if it should be)
> net user $USER
$ net user lavr
The user name could not be found.
I don't have local users on this PC except for two maintenance accounts ('net
user' shows them,
but they are not mine, and they are for our systems team, who administrates the
machine).
My account is a domain account here. And everything worked before I had to
change my password.
TIA,
Anton Lavrentiev
Contractor NIH/NLM/NCBI
--
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
Re: Unable to start Cygwin64 terminal after password change
On 2021-07-31 15:09, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote: I seem to be unable to start "Cygwin64 Terminal" (using the standard icon placed on the desktop when Cygwin gets installed) after I had to change my password (at work). My account did not change. What I see is that the terminal window pops up momentarily with a text "This account is currently not available", and then closes right away. I'm using my work PC perfectly fine, and my new password works just as well (using it every time to log in the system), only the Cygwin terminal stopped working after the change. I "own" the Cygwin installation on my work PC (it's installed by me from under my username). Even rebooting the PC did not help to clear this up. Weirdly enough, I can start bash from cmd.exe, but then it shows my username numerically: C:\WINDOWS\system32>c:\cygwin64\bin\bash.exe NCBI_NT+User(1606)@NCBIPC9135 /cygdrive/c/WINDOWS/system32 $ uname -a CYGWIN_NT-10.0 NCBIPC9135 3.2.0(0.340/5/3) 2021-03-29 08:42 x86_64 Cygwin Any suggestions? Maybe show us the outputs from: $ head /proc/version; getent passwd $USER; net user $USER with necessary parts obfuscated. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.] -- 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
Unable to start Cygwin64 terminal after password change
Hi all, I seem to be unable to start "Cygwin64 Terminal" (using the standard icon placed on the desktop when Cygwin gets installed) after I had to change my password (at work). My account did not change. What I see is that the terminal window pops up momentarily with a text "This account is currently not available", and then closes right away. I'm using my work PC perfectly fine, and my new password works just as well (using it every time to log in the system), only the Cygwin terminal stopped working after the change. I "own" the Cygwin installation on my work PC (it's installed by me from under my username). Even rebooting the PC did not help to clear this up. Weirdly enough, I can start bash from cmd.exe, but then it shows my username numerically: C:\WINDOWS\system32>c:\cygwin64\bin\bash.exe NCBI_NT+User(1606)@NCBIPC9135 /cygdrive/c/WINDOWS/system32 $ uname -a CYGWIN_NT-10.0 NCBIPC9135 3.2.0(0.340/5/3) 2021-03-29 08:42 x86_64 Cygwin Any suggestions? Thanks, Anton Lavrentiev Contractor NIH/NLM/NCBI -- 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
