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 Stops Responding After Extended Period of Inactivity #1065

Closed
JamesDrummond opened this issue Oct 31, 2016 · 5 comments
Closed

Terminal Stops Responding After Extended Period of Inactivity #1065

JamesDrummond opened this issue Oct 31, 2016 · 5 comments

Comments

@JamesDrummond
Copy link

When I have a terminal open in a workspace for an extend period of inactivity it will stop responding to input. I can create a new terminal that will work. I am using the hackathon version. I extended my workspace timeout so I am not sure if there is the same problem for codenvy.io as the workspace will time before I can test.

Codenvy version: Hackathon. I am not sure if it effects any other onprem versions with extended workspace time configured.
OS and version: Debian - Linode server 4 core 16 gb ram.

Additional information:

Problem only started happening recently, didn't happen in an older version of Codenvy: Not sure.
Problem can be reliably reproduced: Yes. Wait for about an hour with no activity.

@garagatyi
Copy link
Contributor

Can you describe environment where you run this instance? Is it on some remote instance? Is there a proxy between you and terminal?

@JamesDrummond
Copy link
Author

@garagatyi No proxy. I am running a the hackathon version with all server resources and no external nodes on Debian Linode server. I just had it happen again. This time I tried getting out of then into the workspace and I get a workspace not found error message. However the workspace is still accessible. Might be a new issue entirely. The screen capture below doesn't show the terminal responding(forgot to record) but does show the new error message and IDE not functioning correctly.

issue1

@garagatyi
Copy link
Contributor

I believe it is completely separated issue. Please create an issue for that bug.

From your IP I suppose that it is remote to your browser, e.g. it is not on your local PC/laptop. So you can't know if there is a proxy (even hidden from you, without any configuration on your side) between you and container.

I believe we should explore lack of response from terminal from websocket connection side - our current implementation doesn't send ping packets into websocket connection.

@JamesDrummond
Copy link
Author

Opened a new issue to track this as the terminal not working is a smaller symptom of a larger problem. #1082

@garagatyi How can I trace the client/server connection to see if there is a proxy between?

@garagatyi
Copy link
Contributor

I do believe that these 2 problems are unrelated to each other.

How can I trace the client/server connection to see if there is a proxy between?
I don't think you can do that. Probably we should just test it in controlled environment. Maybe we will get more information if someone else submit the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants