Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terminal in connecting... #8033

Open
cherry-koerber opened this issue Mar 21, 2024 · 1 comment
Open

Terminal in connecting... #8033

cherry-koerber opened this issue Mar 21, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@cherry-koerber
Copy link

cherry-koerber commented Mar 21, 2024

Describe the bug
A clear and concise description of what the bug is.
When open a terminal on windows 10 machine
image
image

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

  • Lens Version:
  • OS: [e.g. OSX]
  • Installation method (e.g. snap or AppImage in Linux):

Logs:
When you run the application executable from command line you will see some logging output. Please paste them here:

error: [SHELL-SESSION]: failed to open a local shell Error launching WinPTY agent: Security check failed: pipe client pid (6940) does not match agent pid (18204) {"stack":"Error: Error launching WinPTY agent: Security check failed: pipe client pid (6940) does not match agent pid (18204)\n    at new WindowsPtyAgent (C:\\Users\\ChandraSekharMallu\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\node-pty\\lib\\windowsPtyAgent.js:83:36)\n    at new WindowsTerminal (C:\\Users\\ChandraSekharMallu\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\node-pty\\lib\\windowsTerminal.js:51:24)\n    at spawn (C:\\Users\\ChandraSekharMallu\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\node-pty\\lib\\index.js:29:12)\n    at C:\\Users\\ChandraSekharMallu\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\@lensapp\\core-main\\dist\\index.js:3982:17\n    at getOrInsertWith (C:\\Users\\ChandraSekharMallu\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\@lensapp\\utilities\\dist\\index.js:697:19)\n    at ensureShellProcess (C:\\Users\\ChandraSekharMallu\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\@lensapp\\core-main\\dist\\index.js:3979:69)\n    at Object.openShellProcess (C:\\Users\\ChandraSekharMallu\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\@lensapp\\core-main\\dist\\index.js:3997:42)\n    at async C:\\Users\\ChandraSekharMallu\\AppData\\Local\\Programs\\Lens\\resources\\app.asar\\node_modules\\@lensapp\\core-main\\dist\\index.js:4132:7"}

Kubeconfig:
Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information.

your kubeconfig here

Additional context
Add any other context about the problem here.

@cherry-koerber cherry-koerber added the bug Something isn't working label Mar 21, 2024
@Tixon123
Copy link

Tixon123 commented Apr 3, 2024

Hello cherry-koerber,

Thank you for reaching out to Lens support!

Thank you for reporting a bug.

We are working on your issue. Stand by for further updates.

Best Regards,
Tikhon Kudinov
Lens Support Engineer
Mirantis, Inc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants