This message was deleted.
# citrix-vad
s
This message was deleted.
j
smells like someone is trying to power on/off at the hypervisor level, and then the power settings at the Citrix side is saying "errrr no", Check your DG load based settings and power management policies?
s
remember 20 mins is the default time to register after a shutdown/reboot. If you have a lot of VDAs and the backend storage/infra is struggling, you can change the default 20 mins, or you can reboot them over a longer period of time instead of all at once. And check the simultaneous connections at the hosting connection level. Also, if you think the DG has some weird settings, you can always create a new DG and move the VDAs.
j
Thanks, lads. Iโ€™ll have a look in the AM. It wonโ€™t be a load issue. At this stage, itโ€™s just 3 MC/DGs with 1 VDA in each. It was working fine for testing until daily reboots schedules were added on Thursday, cheers
s
AHV?
j
VMware bud
j
by load i mean like peak time settings etc
sorry, should have described better - check the TZ on the DG as well
๐Ÿ‘ 1
j
No issues with TZ, zero policies applied or anything a miss with load/peak processing, etc. 1 of the 3 affected has come back to life. 2 are still an issue; tried creating fresh MCs/DGs, but will not register with 'Stuck on Boot' error in Director. The client cloned these VDAs and done an in place upgrade. They were working fine for weeks, only change was adding the restart schedule. I think Im going to run the removal/cleanup tool and reinstall the VDA on those affected.. sigh! Cheers
Another point, the client advised he can see the ctx svc account configured in the hosting connection disconnecting the nic. Is this normal behaviour when power-managing persistent/non-MCS VDAs? Cheers
n
What do you mean by the last thing, it shouldnt d/c the NIC - what youll see is "Reconfiguring virtual machine" or a straight out power action kicked off by the svc account in the VMware log
j
Yo, in most cases, the shutdown command is initiated by the svc account via the hosting connection, then the VDA is powered on but the nic is disconnected (in vsphere vmware settings). The option / checkbox on the VM is connect at poweron but something is clearing this.. so the VDA is up with no network and cant register, then shuts down after 20 mins (timeout limit)
I have no access to vmware, the client is sure its not a vmware issue.. Im going to hop on a call and pull in ctx, cheers
Thanks guys, the client confirmed they messed something up on the VMware side when running the cloning process, all good now, cheers
๐Ÿ˜€ 1
s
As soon as you said the client is sure it isnt a vmware issue, I would have put money down that it was, on the simple fact that nothing is 100% when dealing with technology. Glad you got it sorted.
j
Cheers, Steve ๐Ÿ™‚
n
This was a great thread to follow JG ๐Ÿ™‚
๐Ÿ™ƒ 1