You are not logged in.
Pages: 1
Hi there,
I've been using Slitaz 4.0 to host a small web app of mine.
It runs lighttpd and php.
My app requires real time updates from the server, and up until now I used ajax frequent polling with no problems.
Since I found stupid I had to poll so frequently, I looked around and decided to implement a websocket solution. But then the problem appeared.
Basically while I can constantly poll lighttpd without problems, connecting to my websocket port repeatedly seems to give a hard time to slitaz.
Here is the behaviour I first observed: I have my websocket server listening on port 9000 and do my stuff with the app. Now and then my ssh/sftp connection to the slitaz box will go down, together with lighttpd (I can't load any page on the server). Sometimes ssh doesn't fall but lighttpd does, and I can check that the box is still running by executing commands or restarting lighttpd. Sometimes I try to reconnect with my sftp client when I get disconnected, but I won't be able to. After 2/3 minutes I am able to restore ssh connections and load web pages. In the meantime the box did not restart.
At first I thought it was the websocket server's fault, and turned it down.
I reloaded my webapp, which is instructed to try and reconnect to the ws server if the connection goes down. The app would hence try and connect every second, and fail.
If I let the app do this for a while (say 30 connection failures), then the same symptoms appear: unable to load webpages (lighttpd not responding), occasional failure of ssh/sftp.
I hence feel the problem has to do with the tcp connection started by my browser to my ws server, and not by the ws server itself.
Is there any common reason why the connections "jam up" and stop working for a while?
Do you have any ideas on how I may debug this? I'd really like to keep slitaz as it has such a small footprint (I'm running it from a virtual machine using about 50mb of ram when under stress).
Thanks for any help, suggestions
Offline
Pages: 1
[ Generated in 0.016 seconds, 7 queries executed - Memory usage: 1.53 MiB (Peak: 1.77 MiB) ]