Elsinore

User Forum

www.screenconnect.com
Welcome Guest Search | Active Topics | Log In | Register

Tag as favorite
ScreenConnect_2.4.2335.4429 - High CPU and Relay nonresponsive
MeatGeeksBBQ
#1 Posted : Monday, February 20, 2012 1:16:27 AM
Rank: Newbie
Joined: 5/6/2011
Posts: 4
Location: Atlanta, GA
Since installing ScreenConnect_2.4 (many versions of the pre-release have been tried), I get almost hourly instances of the ScreenConnect.Service.exe pegging out at 90+% and the relay service appearing to lockup. I can restart the Relay service and it helps, but only for a short period of time.

It seems to be an exponential issue in that after it begins...the time between instances of the problem shortens until a server reboot, then after a reboot I get from 6 to 8 hours until it happens again. This is a Windows 2008 R2 server.

With 2.3 it was as stable a program as I have seen..I know 2.4 is preRelease, so I know there are potential pitfalls...just wondering if there are any bandaids until the production 2.4 comes out.

Thanks
Jake Morgan
#2 Posted : Monday, February 20, 2012 1:23:07 PM
Rank: Administration
Joined: 4/9/2010
Posts: 872
Can you give our support line a call this morning? We'd like to get this straightened out.
mdawes
#3 Posted : Tuesday, February 21, 2012 8:51:54 AM
Rank: Newbie
Joined: 2/21/2012
Posts: 4
Location: Ipswich
Sounds similar to issues we are having with Screenconnect 2.4 - I dont think we have the high CPU usage. The relay seems a bit more stable on port 443 - on port 80 it was falling over once every hour or so - on 443 it seems to be 2 or 3 times a day. I did try to create a batch file that stops and starts all the services, but it dosnt seem to like being done that way, but works OK when I manually stop/start them....

We are also W2008 (web edition) - SP2
Jake Morgan
#4 Posted : Tuesday, February 21, 2012 10:28:10 PM
Rank: Administration
Joined: 4/9/2010
Posts: 872
I think we've gotten to the bottom of this one. We didn't expect our connection "accepts" to fail non-fatally. However, accepts can apparently fail, probably when severed by a DPI device. This is why we experience different behavior on different ports. Once we use up our pre-allocated set of accepts in our accept pool, relay stops responding.

Also older unattendeds don't behave very nicely when their connections get severed like this. Since the connection was originally established correctly, they don't wait 5 seconds to retry-- they retry immediately. They'll essentially DDoS your Relay. This was fixed a while back, but even 5 or 10 of the older guys connecting constantly can put a big load on relay.
mdawes
#5 Posted : Friday, February 24, 2012 4:46:01 PM
Rank: Newbie
Joined: 2/21/2012
Posts: 4
Location: Ipswich
Hi Jake - Does this mean it will constantly happen - or will it be able to be fixed in a future release? We have the issue still ongoing on a fresh install - do you mean that older unattended installs will be causing the issue?

Many Thanks,

Mark Dawes
Users browsing this topic
Guest
Tag as favorite
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.