You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
The text was updated successfully, but these errors were encountered: