100% CPU after interrupted connection

5 posts / 0 new
Last post
Iedjee
100% CPU after interrupted connection

Hi Michael, i use the Virtualhere server on my OpenWrt RT3xxx router. Sometimes my Wifi connection is not that stable and connection from the client gets interrupted.
When it connects again it will show "in use by ...". Off course i can disconnect the user in the --admin mode of the client, but the CPU of the server is already at 100% (permanent!), making the Wifi very slow and connection almost impossible.

Wouldn't it be better to just disconnect the user at the server when the TCP/IP-connection gets interrupted ? Or maybe there is another solution for this problem?

My workaround is that i have to log on to the router, search the procesnumber of the Virtualhere server with "ps" and "kill" that proces by its number, then restart the server...

I hope to hear from you. Greetings, Evert

Michael
Hi Evert, actually

Hi Evert, actually virtualhere already does automatically disconnect the user if there is a TCP error or a client ping timeout. If its getting jammed its probably because it is getting no response from the openwrt kernel when it should get one. Do you have gdb on your openwrt box?

If so i will compile a debug version of the server for you. When it gets jammed just run "gdb attach " then "thread apply all bt" that will show where it is getting stuck.

Iedjee
Yes, I managed to install gdb

Yes, I managed to install gdb through the entware-repository. I now have:

/opt/etc # gdb --version
GNU gdb (GDB) 7.3.1
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "mipsel-linux-gnu".
For bug reporting instructions, please see:
.

Michael
great!, will send you a link

great!, will send you a link to the debug build

Michael
The 100% cpu problem is

The 100% cpu problem is solved in the latest build of virtualhere for openwrt rt3xxx.

Log in or register to post comments