Jump to content
Welcome to our new Citrix community!
  • 0

XenApp Servers freezing / crashing after image update - VDA 7.15 CU4


Question

Hi, we updated our golden image recently with the latest windows updates and no other major changes.

 

We found that all of the XenApp servers using that image began having problems immediately. As people we starting the day, some people found their sessions froze, and others found as they logged on they got a grey screen.

 

The only way to fix it was to roll back the image and the problem went away.

 

To test the image I've created a machine catalog with one machine and the suspect image.

 

It has happened a couple of times since and noticed that the CPU spikes up at the time people get the problem.

 

I'm not able to log onto the XenApp server at the time though to retrieve the logs, even through the VMWare console.

 

They are non persistent machines so it doesn't save the logs.

 

Is there a way I could capture what is happening? I find when the problem occurs we reboot the XenApp server and never get to find out what happened

 

In the delivery controller event there is this but it doesn't help much I don't think

 

1039 - The Citrix Broker Service failed to contact virtual machine

 

Thanks for any advice

Link to comment

11 answers to this question

Recommended Posts

  • 0

Hey,

 

the answer to this kind of problems is usually in the event viewers of the xenapp servers.

 

If you are losing those logs upon every reboot I recommend making a build update in which you redirect the location for at least all primary event viewer parts (system, application, security) to the persistent drive where your cache file resides (usually D: drive on the virtual xenapp servers which is a local attached drive in vmware settings)

 

Also make sure a memory minidump upon bluescreen is configured inside your master image on this same persistent drive.

 

Then you should be able to trace all event logs properly and see what's happening. Start from there

Link to comment
  • 0

Thanks for this, I couldn't find where the Cache file resides we only have a C: 

 

In Vmware we have

 

Disk 1 - 90gb non persistant

Disk 2 - 16mb

Disk 3 - 80gb

 

In disk management in Server 2008 R2 it shows disk 3 as being un-allocated

 

In vmware the path is [RAW_DS_02] RAW-XA2K8-T-01/RAW-XA2K8-T-01_TemporaryStorage.vmdk

 

Thanks for any advice

Link to comment
  • 0

Hmm assuming you are using PVS with "cache on device RAM with overflow on Hard disk" or "Cache on device HD" you should have at leas 1 formatted partition available on the local attached cache drive which looks like it would be Disk 3. Something like 20-40Gb formatted as D:\ or E:\ drive for instance.

 

When your vm machine boots with pvs disk type in read mode it the PVS agent will cause things like the swap file and write cache settings to go there. If you do not have a formatted partition present it cannot and does not function as it should. Most likely it then falls back to creating the cache file on the PVS server itself in a subdirectory, which is slow.

 

But back to the matter at hand, If you have no partition available on your vm machines you can ofcourse not redirect your event viewer logs to be persistent either.

 

Check if disk 3 was present for that purpose indeed. If it is, create a 20-40GB partition of your choice, format it as NTFS D:\ drive and reboot the vm machine. See what appears on that D: drive then

Link to comment
  • 0
On 7/1/2019 at 2:11 PM, Daniel Dunn1709158952 said:

I dont know if it makes a difference but we use MCS.

 

I've tried the forward and it seems to work ok without any noticeable slow down, its just a temporary thing to see what happens when it crashes.

 

Hi have you found a Solution ?

We had exact the same Problem after Update our Golden Image. 

What we have found is, the following Updates are Installed:

 

KB2843630 
KB2862152 
KB2884846 
KB2892074 
KB2893294 
KB2898514 
KB2898742 
KB2898868 
KB2898871 
KB2901101 
KB2901125 
KB2901128 
KB2906956 
KB2908174 
KB2912390 
KB2913152 
KB2913270 
KB2914218 
KB2922229 
KB2923528 
KB2931358 
KB2931366 
KB2939087 
KB2973201 
KB2976897 
KB2978041 
KB3008242 
KB3010788 
KB3011780 
KB3012235 
KB3013410 
KB3013531 
KB3013538 
KB3015696 
KB3018133 
KB3021674 
KB3027209 
KB3032663 
KB3034348 
KB3037924 
KB3042058 
KB3043812 
KB3048043 
KB3074228 
KB3076949 
KB3081320 
KB3087041 
KB3092601 
KB3092627 
KB3102939 
KB3115858 
KB3126041 
KB3126593 
KB3132080 
KB3138378 
KB3146978 
KB3149157 
KB4462930 
KB4486105 
KB4486111 
KB4514371 
KB4515846 
KB4515853 
KB4516115 
KB4519567 
KB4521864 
KB4520012

 

one Update must be the Problem there.

Link to comment
  • 0

We have found that Citrix Elastic Layer 19.10 is the Problem. When we Restored an Backup from Version 19.07 an Recreate all Images new. Then no more Probem with Freezes. 
The Problrem must on Verison 19.10. 

 

The Only need ist to Upgrade the Appliance (then the Problem ist there) for us we wait of an new Version. An let den ELM to VErsion 19.07 as Workaround. 

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...