From: "Fournier, Danny G" <Danny.Fournier@dfo-mpo.gc.ca>
To: "Gluszczak, Glenn" <Glenn.Gluszczak@dell.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: ERROR: A specified logon session does not exist. It may already have been terminated
Date: Tue, 17 Oct 2017 19:32:00 -0000 [thread overview]
Message-ID: <513AA0729B894545B2D793D01FFF8B6D471A0D3B@SVNSBIOMBX01.ENT.dfo-mpo.ca> (raw)
In-Reply-To: <91DCAC3CB99C724EB365BB64677FBE7B1EFC501E@MX204CL04.corp.emc.com>
Here's what I just did:
1. created new local administrator account
2. ran mkpasswd -l > /etc/passwd
3. removed all instances of server name in /etc/passwd (ie. MYSERVERNAME+)
4. remotely connected successfully
5. successfully ran schtasks, it listed all jobs configured
I just retried with the other user, where I connect specifying a shared key and got the error message.
For good measure, I changed the password on the problematic user, connected directly without the key and provided the password. I then ran schtasks and it ran fine. It listed all the jobs configured.
It would seem that our issue is related to connecting over SSH using a shared key.
-----Original Message-----
From: Gluszczak, Glenn [mailto:Glenn.Gluszczak@dell.com]
Sent: October-17-17 11:08 AM
To: Fournier, Danny G
Subject: RE: ERROR: A specified logon session does not exist. It may already have been terminated
Does ssh with Administrator and running schtasks fail as well?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-10-17 19:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 14:38 Fournier, Danny G
2017-10-10 14:48 ` Gluszczak, Glenn
2017-10-10 15:03 ` Fournier, Danny G
2017-10-10 15:14 ` Gluszczak, Glenn
2017-10-10 16:54 ` Fournier, Danny G
[not found] ` <91DCAC3CB99C724EB365BB64677FBE7B1EFC1C9B@MX204CL04.corp.emc.com>
[not found] ` <513AA0729B894545B2D793D01FFF8B6D471A0719@SVNSBIOMBX01.ENT.dfo-mpo.ca>
[not found] ` <91DCAC3CB99C724EB365BB64677FBE7B1EFC501E@MX204CL04.corp.emc.com>
2017-10-17 19:32 ` Fournier, Danny G [this message]
[not found] ` <91DCAC3CB99C724EB365BB64677FBE7B1EFC5305@MX204CL04.corp.emc.com>
2017-10-18 12:04 ` Fournier, Danny G
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=513AA0729B894545B2D793D01FFF8B6D471A0D3B@SVNSBIOMBX01.ENT.dfo-mpo.ca \
--to=danny.fournier@dfo-mpo.gc.ca \
--cc=Glenn.Gluszczak@dell.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).