Jump to content


Photo

Machines don't always start after scheduled Reboot

Started by Tarik Chougui , 20 April 2015 - 12:41 PM
36 replies to this topic

L. T. Zwanenburg Members
  • #21

L. T. Zwanenburg
  • 6 posts

Posted 17 January 2017 - 10:35 AM

I think there is a differens in the update order.

We Always first update The Delivery Controllers\Director and then the VDA's.

I think the official way is first VDA's and then the Controllers.

 

Remove the reboot schedule and then recreate it is only working when the controllers are 7.12

(Controllers take the action to reboot an server)

 

After updated the controllers the reboot schedules where not working. (all versions VDA's)

ater recreating them it works fine.

 

So i do not know what happens when you first update the VDA's to 7.12 and the controler is still an older version.

I Think recreating the scheduler is not working in that case because the controller take the action to reboot.



Martin Stratmann Members
  • #22

Martin Stratmann
  • 10 posts

Posted 17 January 2017 - 11:06 AM

We have the same problem since we´ve updated from 7.6 FP3 to 7.12. Schedule reboots don´t work no more for each existing desktop group. I´ve created a new one with 7.9 or new features, added a server to this group.and set up a schedule reboot... That works!

 

We updated controller first, then the VDA´s. I´m going to remove the schedule reboot, recreate it and let you know tomorrow if that was the solution-

 

BR

Martin



pjoppen371 Members
  • #23

Patrick Joppen
  • 4 posts

Posted 20 January 2017 - 07:00 AM

We solved the Problem by Using VDA 7.11 

it seems to be a problem of the VDA 7.12 -> after downgrading the VDA to 7.11 in the Master Images the Reboot schedule is working fine.



Martin Stratmann Members
  • #24

Martin Stratmann
  • 10 posts

Posted 20 January 2017 - 07:52 AM

Sorry for late response. Deleting and recreating of schedule reboot task via Studio didn´t fix it. 

 

Creating schedule tasks via  New-BrokerRebootScheduleV2 (decribed here) has done the job! It´s circuitous, but it works!

 

 

 

 

Francois Callens Members
  • #25

Francois Callens
  • 3 posts

Posted 20 January 2017 - 05:30 PM

Hello All,

 

I am new on this forum, and I read carefully all your messages. We meet exactly the same problem with reboot not working.

 

We upgraded from 7.8 to 7.12 last december (DDC + VDA), and since that moment scheduled reboots are not working properly.

 

In fact it works if the VDA server has no opened session. In the other way the server is skipped.

 

I tried to delete all the existing reboot schedule with the powershell command, and then recreate them with the "V2" commands (New-BrokerRebootScheduleV2). No success. I tried to add tags also, no success -> reboots don't work, with abandonned status in event.

 

I didn't try to downgrade the VDA agent version, I hope there is another solution with the VDA 7.12.

 

Francois



Adam Wingler Members
  • #26

Adam Wingler
  • 15 posts

Posted 20 January 2017 - 07:35 PM

There is a private hotfix available to address VDA's not rebooting at their scheduled time after upgrading to 7.12.



Christian Hock Members
  • #27

Christian Hock
  • 102 posts

Posted 23 January 2017 - 07:06 AM

Where we can download this fix?



Francois Callens Members
  • #28

Francois Callens
  • 3 posts

Posted 23 January 2017 - 03:42 PM

You may ask it to Citrix support, because it is a private fix



Christian Hock Members
  • #29

Christian Hock
  • 102 posts

Posted 31 January 2017 - 09:36 AM

Solution:

 

https://jhmeier.com/2017/01/23/scheduled-reboots-not-working-on-citrix-xendesktop-7-12/



Chris James Members
  • #30

Chris James
  • 2 posts

Posted 20 March 2017 - 10:11 PM

Those of you having this problem, do your provisioned servers have a SCSI Adapter? Not sure if this fixed mine, but I've added the SCSI adapter, and my server now restart when scheduled with no issue.

 

Previously, one server would restart and then shutdown after 20 minutes, and the other would not reboot at all. Upgraded to 7.13 recently, but after reboot both servers shut down. So I'm going to (at the moment) assume the scsi adapter is the fix. I couldn't even live migrate in SCVMM, but now I can manage that task too.



Nils Andreas Myhre Members
  • #31

Nils Andreas Myhre
  • 2 posts

Posted 28 April 2017 - 07:01 AM

Can you share a little more about your enviroment Chris?

 

What kind of SCSI adapter? What hypervisor are you running?

I too have this problem, even after upgrading to 7.13 where LC6766 is included.

Those of you having this problem, do your provisioned servers have a SCSI Adapter? Not sure if this fixed mine, but I've added the SCSI adapter, and my server now restart when scheduled with no issue.

 

Previously, one server would restart and then shutdown after 20 minutes, and the other would not reboot at all. Upgraded to 7.13 recently, but after reboot both servers shut down. So I'm going to (at the moment) assume the scsi adapter is the fix. I couldn't even live migrate in SCVMM, but now I can manage that task too.



leitstelletirol Members
  • #32

IT Leitstelle Tirol
  • 20 posts

Posted 26 May 2017 - 07:49 AM

yep... still the same problem on 7.13



Adam Holzberger Members
  • #33

Adam Holzberger
  • 12 posts

Posted 26 June 2017 - 10:47 AM

Still the same problem on 7.13 with different customers.



Aaron Barker Members
  • #34

Aaron Barker
  • 2 posts

Posted 18 July 2017 - 07:34 PM

I am having a similar problem. I use a PowerShell script to restart our XenApp 7.13 servers. The vSphere task log shows a task called "VirtualMachine.shutdownGuest.label", which is the initial shutdown command sent by MCS. Another task called "VirtualMachine.powerOn.label" is sent, which powers the server back on, but the server does not boot. The console shows a black screen and the server is not responsive. After about 20 to 30 minutes, XenApp still shows the server as powered on but unregistered, and a new task is sent to vSphere to shut down the guest OS again. This task fails, and is followed by a power off task.

 

This doesn't happen for every server, but a lot of them. When I use Citrix Studio to start the servers that failed to boot, some of them start successfully and some don't. They power on but don't complete the boot process. Eventually I can get them all to start by trying several times.



leitstelletirol Members
  • #35

IT Leitstelle Tirol
  • 20 posts

Posted 19 July 2017 - 08:35 AM

i could solve our issue with the reboots. We had a faulty printer driver which blocked shutdowns and for some reason sometimes he also blocked the booting process.

 

i preinstalled the driver on the master images instead of deploying it via point-and-print group policy. now everything works fine.



RYAN CAMPBELL Members
  • #36

RYAN CAMPBELL
  • 98 posts

Posted 14 September 2017 - 10:19 PM

Have been seeing the same inconsistent issue, with 2008 R2 VDA's.

7.14 on controllers and VDA.

 

Following the trail I see, the reboot schedule action fire to vCenter as a power off action.

When things work good, I see a power on action and everything is happy.

 

When things go bad I do not see the power on action, but following PVS logs I see the machine boot.  But likely get hung on boot, then I see another poweroff action from the controller.  Assuming there is a timeout from the controller looking for the VDA to register after a scheduled reboot action, and when it doesn't see it in a certain time-frame it just powers the VDA off again.

 

I think my issue here is related to intermittent boot hang on PVS VDA's.

Any idea on how to tweak the controller behaviour to power on again after a power off action?



RYAN CAMPBELL Members
  • #37

RYAN CAMPBELL
  • 98 posts

Posted 15 September 2017 - 02:29 PM

Have been seeing the same inconsistent issue, with 2008 R2 VDA's.

7.14 on controllers and VDA.

 

Following the trail I see, the reboot schedule action fire to vCenter as a power off action.

When things work good, I see a power on action and everything is happy.

 

When things go bad I do not see the power on action, but following PVS logs I see the machine boot.  But likely get hung on boot, then I see another poweroff action from the controller.  Assuming there is a timeout from the controller looking for the VDA to register after a scheduled reboot action, and when it doesn't see it in a certain time-frame it just powers the VDA off again.

 

I think my issue here is related to intermittent boot hang on PVS VDA's.

Any idea on how to tweak the controller behaviour to power on again after a power off action?

 

I believe I found the fix in my case, from Patrick in:

https://discussions.citrix.com/topic/382996-xa-711712-win2012r2-vdas-do-not-boot-after-scheduled-restart/

 

Add the following registry key on Deliverry Controller

 

To enable the fix, set the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\DesktopServer\RebootSchedule
Name: ShutdownTimeoutRecovery
Type: DWORD
Value: 1

 

To disable the fix, set the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\DesktopServer\RebootSchedule
Name: ShutdownTimeoutRecovery
Type: DWORD
Value: 0

 

https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-9/whats-new/fixed-issues.html

 

Seems to have resolved the issue, fingers crossed.