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

stuck creating pty? #103

Closed
risacher opened this issue Nov 14, 2013 · 2 comments
Closed

stuck creating pty? #103

risacher opened this issue Nov 14, 2013 · 2 comments

Comments

@risacher
Copy link

I have two Ubuntu servers, each running tty.js - one works fine all the time, but the other gets "stuck" after a day or two. The user experience is that when the "Open Terminal" button is clicked, a black window opens but no process is spawned.

Based on the console output where tty.js is running, I speculate this has to do with creating ptys... see below. Observe how for Session 17-18 it immediately reports "Created pty..." but when it stops working properly, it stops saying that (Sessions 19-22).

Anyone seen similar behavior or have ideas how to troubleshoot this? If I restart tty.js, the problem goes away for a day or two.

[tty.js] 17 Session 17 created.                                                                                                  
[tty.js] 17 Created pty (id: /dev/pts/2, master: 18, pid: 20593).                                                                
[tty.js] 17 Client disconnected.                                                                                                 
[tty.js] 17 Killing all pty's.                                                                                                   
[tty.js] 17 Closed pty (/dev/pts/2): 18.                                                                                         
[tty.js] 18 Session 18 created.                                                                                                  
[tty.js] 18 Created pty (id: /dev/pts/4, master: 18, pid: 8383).                                                                 
[tty.js] 18 Client disconnected.                                                                                                 
[tty.js] 18 Killing all pty's.                                                                                                   
[tty.js] 18 Closed pty (/dev/pts/4): 18.                                                                                         
[tty.js] 19 Session 19 created.                                                                                                  
[tty.js] 19 Client disconnected.                                                                                                 
[tty.js] 19 Killing all pty's.                                                                                                   
[tty.js] 20 Session 20 created.                                                                                                  
[tty.js] 20 Client disconnected.                                                                                                 
[tty.js] 20 Killing all pty's.                                                                                                   
[tty.js] 21 Session 21 created.                                                                                                  
[tty.js] 22 Session 22 created.                                                                                                  
[tty.js] 21 Client disconnected.                                                                                                 
[tty.js] 21 Killing all pty's.       
@risacher
Copy link
Author

Disregard; sorry.
I still have an issue, but it ain't with creating a pty. I never get a good socket.io connection after the first session.

@risacher
Copy link
Author

Resolution for anyone with similar problem: I was running tty.js behind a reverse-proxy server based on node-http-proxy. Unfortunately, because of http-party/node-http-proxy#444, proxying websockets with node 0.10.x is broken. I solved my problem by switching the proxy server to nginx.

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

No branches or pull requests

1 participant