VMware Horizon Community
Dave_O
Contributor
Contributor
‎03-21-2008 08:46 AM

VDM broker fails to service external requests after several hours

I have set up VDI with a VDM broker for both internal & external use. All works fine apart from the fact that externally after a few hours (7 or 😎 the broker stops servicing vm client requests. Prior to that everything is fine. The broker event log show a few errors (listed below). I have checked the VDM services on the broker and they are running OK. A reboot of the VDM server (which is virtual 2Gb menory single CPU) resolves the issue, but I don't want to keep doing that if it can be avoided. I have load balanced with 2 identical servers to try and reduce the impact but this is having no effect since the relevant services are still running on VDM server and hence there is no trigger to fail over. I know there are solutions address this but they do not really address the real issue, just mitigate against it. Any help or guidance would be appreciated.

Logs

!https://10.229.131.29/admin/images/small_events.gif!ASSERT: id == null (more ...)

!https://10.229.131.29/admin/images/error16x16.gif!ERROR

03/21/2008 03:28:39 PM

Assert

TP-Processor2

!https://10.229.131.29/admin/images/small_events.gif!ASSERT: id == null (more ...)

!https://10.229.131.29/admin/images/error16x16.gif!ERROR

03/21/2008 03:28:39 PM

Assert

TP-Processor2

!https://10.229.131.29/admin/images/small_events.gif!Error retireving user for SID null. (more ...)

!https://10.229.131.29/admin/images/error16x16.gif!ERROR

03/21/2008 03:28:39 PM

Util

TP-Processor2

(Request143) Request failed: com.vmware.vdi.ob.tunnelservice.bk: Failed whilst returning body: java.io.IOException: Broken pipe com.vmware.vdi.ob.tunnelservice.dq.b(SourceFile:164)
com.vmware.vdi.ob.tunnelservice.bk: Failed whilst returning body: java.io.IOException: Broken pipe
	at com.vmware.vdi.ob.tunnelservice.l.a(SourceFile:388)
	at com.vmware.vdi.ob.tunnelservice.l.b(SourceFile:419)
	at com.vmware.vdi.ob.tunnelservice.l.a(SourceFile:226)
	at com.vmware.vdi.ob.tunnelservice.dq.b(SourceFile:162)
	at com.vmware.vdi.ob.tunnelservice.d.run(SourceFile:167)
	at java.lang.Thread.run(Unknown Source)
Caused by: java.io.IOException: Broken pipe
	at simple.http.MonitoredOutputStream.destroy(Unknown Source)
	at simple.http.MonitoredOutputStream.write(Unknown Source)
	at simple.http.ResponseStream.write(Unknown Source)
	at com.vmware.vdi.ob.tunnelservice.dq.a(SourceFile:123)
	at com.vmware.vdi.ob.tunnelservice.l.a(SourceFile:386)
	... 5 more

!https://10.229.131.29/admin/images/small_events.gif!(Request143) Request failed: com.vmware.vdi.ob.tunnelservice.bk: Failed whilst returning body: java.io.IOException: Broken pipe com.vmware.vdi.ob.tunn (more ...)

!https://10.229.131.29/admin/images/error16x16.gif!ERROR

03/21/2008 03:27:58 PM

SimpleAJPService

AJP-43

!https://10.229.131.29/admin/images/small_events.gif!ASSERT: id == null (more ...)

!https://10.229.131.29/admin/images/error16x16.gif!ERROR

03/21/2008 03:23:22 PM

Assert

TP-Processor3

!https://10.229.131.29/admin/images/small_events.gif!ASSERT: id == null (more ...)

!https://10.229.131.29/admin/images/error16x16.gif!ERROR

03/21/2008 03:23:22 PM

Assert

TP-Processor3

!https://10.229.131.29/admin/images/small_events.gif!Error retireving user for SID null. (more ...)

!https://10.229.131.29/admin/images/error16x16.gif!ERROR

03/21/2008 03:23:22 PM

Tags (1)
0 Kudos
70 Replies
tonn_s
Contributor
Contributor
‎09-02-2008 03:26 AM

Have following files. see attachement

do you need all files or some of them?

kind regards

sergej

Preview file
88 KB
0 Kudos
marci_s
Contributor
Contributor
‎09-08-2008 10:15 AM

I

0 Kudos
tonn_s
Contributor
Contributor
‎09-08-2008 10:24 AM

Hello i am on vacation till 29.09.

Sergej

0 Kudos
tonn_s
Contributor
Contributor
‎10-02-2008 06:22 AM

Hello Frank,

did you find something? Was the snapshop ok?

Sergej

0 Kudos
ark9898
Contributor
Contributor
‎10-03-2008 01:15 PM

Has this issue been resolved? Currently I have 80 virtual machines running in my environment and lately this has become more than a nuissance. I have to restart the service at least once a day.

0 Kudos
tonn_s
Contributor
Contributor
‎10-08-2008 02:21 AM

Hello Frank,

are the Files OK?

Sergej

0 Kudos
Frank_Taylor1
Enthusiast
Enthusiast
‎10-08-2008 08:50 AM

Sergej,

Sorry for the delay. I am working in our US office this week.

I have downloaded the files but will not get chance to try them out until next week when I am back in the London office.

Thanks,

Frank.

0 Kudos
tonn_s
Contributor
Contributor
‎10-20-2008 02:04 AM

Hi Frank,

did you looked at the files?

Thanks,

Sergej

0 Kudos
tonn_s
Contributor
Contributor
‎10-28-2008 01:26 AM

Hi Frank,

had a new Snapshot. Need FTP directory to upload.

Thanks

Sergej

0 Kudos
tonn_s
Contributor
Contributor
‎11-12-2008 06:57 AM

Hi Frank,

did you get the files? Were the Files OK?

Thanks,

Sergej

0 Kudos
dougdavis22
Hot Shot
Hot Shot
‎11-12-2008 02:05 PM

All,

I've been investigating this very same issue for the past couple of months, and VMware Support recently suggested upgrading the Terminal Service Client on the VDM Connection Server to version 6 (we were running 5.2).

That was over 3 weeks ago now, and so far we have not experienced a repeat of this issue. Having said that, I have kept the SR open for the time being as we have had periods of stability for up to 1 month but prior to the TS Client upgrade we were seeing the problem at least a couple of times a week.

Not sure if anyone else has done this yet, but thought I would share my experience.

Rgds,

Doug.

0 Kudos
csimwong
Contributor
Contributor
‎12-09-2008 11:23 AM

Hello. We experienced a similar issue last night where the web page that users and admins use to login would not come up. The VDM services were up and running. I just ended up rebooting the whole VDM server which got everything working again, but I'd like to know the cause to avoid it happening again.

Has anyone been able to resolved this issue?

Any info would be greatly appreciated. Thanks.

0 Kudos
SurfControl
Enthusiast
Enthusiast
‎01-23-2009 06:26 AM

I'm having the similar issue with the connection server (view 3.0), has anyone found a fix for this problem yet?

0 Kudos
tonn_s
Contributor
Contributor
‎01-23-2009 06:28 AM

Guten Tag!

Bin am 26.01.2009 wieder im Haus.

In dringenden Fällen können Sie sich an die Support-Hotline wenden -234.

Mit freundlichen Grüßen

Sergej Tonn

PS: Ihre Mail wird nicht weitergeleitet.

0 Kudos
dougdavis22
Hot Shot
Hot Shot
‎01-23-2009 02:53 PM

SurfControl,

It's very interesting to hear that you're having the issue with the latest version (View 3.0) - especially as VMware suggested I should upgrade to this version to make the problem go away in my VDM 2.1 environment!!

I'd like to provide an update on where I am with this situation with VMware:

After my previous post on this thread where I stated I'd had uptime for about 3 weeks, I had another few weeks before the same issue reared it's ugly head again. So, I re-opened the SR with VMware Support and had it pushed back up to a P1 and had it escalated so that a Support Manager was assigned to keep on top of progress. As I understand it, there are a number of customers who are having the exact same issues and who have also got high priority calls open with VMware for this. The latest news is that they believe they understand the root cause of the issue, and have been testing a one-off patch for VDM 2.1 with a customer for the past couple of weeks. Should this resolve the issue, they will be providing the patch to all those customers who currently have support calls open for them to apply in their environments.

I'm not entirely convinced, but I have to say it's a lot more hopeful than anything else they've suggested in the last few months that this has been happening. If they do suggest I implement the patch, I will post to this thread again once I have done so and let everyone know the outcome.

As for the fact it's potentially a problem in View 3.0 too, I hope they now know what's wrong and get it fixed in that version too!

Doug.

0 Kudos
Speedbmp
Enthusiast
Enthusiast
‎01-23-2009 03:10 PM

I had a case open with them for the 2.1 problem. they checked out our setup and could find nothing wrong.

then the 2.1.1 came out i then upgraded our setup to that version.

the problem went away.

then view 3.0 came out i then upgraded our network to that version and have been running on that for quite some time with no problems.

Stephen

0 Kudos
dougdavis22
Hot Shot
Hot Shot
‎01-24-2009 01:35 AM

Speedbmp,

How is VDM/View setup in your environment? Are you running Security & Connection Servers or just Connection? Are the servers physical/virtual? What spec are the servers? How many VDis do you have being accessed & how many concurrent users?

Rgds,

Doug.

0 Kudos
Speedbmp
Enthusiast
Enthusiast
‎01-24-2009 07:03 AM

Dougdavis22,

i am running 4 connection servers all Virtual.

i have 2 setup for inside with direct connection, also they are setup for NLB. they are also useing there own URL i.e. vdm.mycompany.com

i then have 2 setup for out side access, with direct connect turned off, also setup with NLB, they also have there own URL say vdmoutside.mycompany.com

the servers each have 1 gig of ram.

at this point i am running about 25 users, I will be expanding the number of users. The users can access there Virtual machines, other users can access the physical computers, and also have it setup for them to access our citrix terminal server

I hope that helps

Stephen

0 Kudos
SurfControl
Enthusiast
Enthusiast
‎01-26-2009 06:08 AM

yes, i'm running View 3.0(in-place upgrade from 2.1), I had this same problem when i was on 2.1 and now I'm on 3.0, the problem is still there...

0 Kudos
Huw_Michael
Contributor
Contributor
‎02-01-2009 01:13 PM

We've had exactly the same problem and it's been intermittent ever since September when we went live with VDM 2.1. Although it's less frequent on View 3.0 it is still there. Same symptoms: unresponsive web interface and broker but all services running and health of the broker server seems fine. I've had support calls open with VMWARE for this issue in VDM 2.1 and View 3.0 but on each ocassion we were required to upgrade every component of the system i.e. broker, agent, vmware tools, esx, virtualcentre before the support guys would investigate the problem and then (frustratingly) we were unable to reproduce it so the call was closed. VMWARE haven't ackowledged this problem to us so it's nice to have it confirmed that we're not the only ones having it.

I see that VIEW 3.1 is out so we will be upgrading to this asap to see if it helps. Until then we continue to reboot on a schedule and will be reviewing Microsoft's 1st VDI attempt in Server 2008 R2 Beta.

Please please please post if you have further information on a fix, and thanks for keeping this thread going.

0 Kudos