Linux VDA stuck on Initializing State

[Przemyslaw Mantaj]

My environment:

• VirtualApps 1912 LTSR
• Linux VDA 1912 LTSR on Centos 7.7

 

I installed Linux VDA with success. It means that:

• Linux joined to domain controller correctly
• I can log in through ssh on my domain credentials.
• I added VDA correctly to Machine Catalog and the Registered State appeared.

 

The problem is that after adding the VDA to the Delivery Group the VDA changes state from Registered to Initializing.

 

Sometimes, in vda log I see error like that:

[BrokerAgent] [Error] RegistrationManager.ResynchroniseSystemTime: Process failed to be started, Exception:System.ComponentModel.Win32Exception (2):
 No such file or directory
   at System.Diagnostics.Process.StartCore(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at Citrix.Cds.BrokerAgent.RegistrationManager.ResynchoniseSystemTime()

I verified NTP server and time synchronisation is correct.

 

Has anyone encountered a similar problem before?

[Przemyslaw Mantaj]

We found a better workaround.

 

We had to unassign all Load Management policies only.  After that, all Linux VDAs started working correctly. If anyone could find any explanation for this, I would be grateful.

[Qian Wang]

Hi, 

May I know how you setup the LinuxVDA env, with MCS or easyinstall?

Can you check if ctxvda service failed to start?

How is dotnet runtime installed? Is the path configured correctly in Registry?

 

Thanks,

Qian

[Przemyslaw Mantaj]

Hi Qian,

 

Thank you for the response. I am using easyinstall setup.

 

ctxvda service status

ctxvda.service - Citrix DotNet VDA Service
   Loaded: loaded (/etc/systemd/system/ctxvda.service; enabled; vendor preset: disabled)
   Active: active (running) since Mon 2020-09-28 11:45:03 CEST; 7min ago
 Main PID: 3364 (ctxvda)
   CGroup: /system.slice/ctxvda.service
           ├─3364 /bin/sh /opt/Citrix/VDA/sbin/ctxvda
           └─3370 /usr/bin/dotnet /opt/Citrix/VDA/lib64/BrokerAgentLinux.dll

Sep 28 11:45:03 xxxxxx systemd[1]: Started Citrix DotNet VDA Service.

DotNet installation:

sudo rpm -Uvh https://packages.microsoft.com/config/centos/7/packages-microsoft-prod.rpm
sudo yum install dotnet-runtime-2.1

DotNet path

$ /opt/Citrix/VDA/bin/ctxreg dump | grep -i dotnet
create -k "HKLM\Software\Citrix\VirtualDesktopAgent" -t "REG_SZ" -v "DotNetRuntimePath" -d "/usr/bin" --force
$ /usr/bin/dotnet --info

Host (useful for support):
  Version: 2.1.22
  Commit:  23677d3ee7

.NET Core SDKs installed:
  No SDKs were found.

.NET Core runtimes installed:
  Microsoft.NETCore.App 2.1.22 [/usr/share/dotnet/shared/Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

 

I thought that Citrix Policies break something after adding the VDA to the DeliveryGroup. I excluded all Citrix Policies from the DeliveryGroup but problem is the same. The strange thing is that when I add the VDA to the Machine Catalog first time I can enumerate linux applications from Start Menu. The problem is when I add the VDA to the Delivery Group and then the state changed from Registered to Initializing.

[Qian Wang]

can you share the detailed vda log under path /var/log/xdl? Initializing usually indicates the first ping from vda is sent to ddc side, but the second ping never reaches ddc.

[Przemyslaw Mantaj]

Log in attachment. Entries from first registration to adding the VDA to the DeliveryGroup.

vda.txt

[Qian Wang]

[2020/09/28 12:53:40.8384245] [BrokerAgentAoTracing] [Information] CONFIGURATION SET Configuration Set Success: VDA machine SID: S-1-5-21-1111-1354286565-637230989-84109, Broker IP addresses: 10.10.63.2, List of blob GUIDs: Citrix.Cds.Protocol.Cbp.PolicyDefinition,Citrix.Cds.Protocol.Cbp.PolicyDefinition, List of tag IDs: NULL_WORKERSETTINGS OR NULL_DESKTOPTAGS, Licensing data: [product:MPS, edition:PLT, model:CCU], Settings hash value: 54831227
[2020/09/28 12:53:41.8822810] [BrokerAgentAoTracing] [Information] REGISTRATION Ping sent: VDA machine SID S-1-5-21-1111-1354286565-637230989-84109, Broker IP: 10.10.63.2, Load value list: [RuleName=CPU, Load=0],[RuleName=Memory, Load=10000],[RuleName=Disk, Load=0], States:  worker [LoadManagementInitializing] windows maint mode [Enable], PVD data: percent done 100 estimated time left 0 error text , Limits: concurrent logins 2 max sessions 250, Message count 0
[2020/09/28 12:54:12.0412763] [BrokerAgentAoTracing] [Information] REGISTRATION Ping response: VDA machine SID S-1-5-21-1111-1354286565-637230989-84109, Broker IP: 10.10.63.2, Heartbeat period: min 30000 max 00:05:00 update threshold 500, Message count: 0, Image out of date: False
[2020/09/28 12:58:01.8247278] [BrokerAgentAoTracing] [Information] BROKER AGENT -> HDX STACK Enumerate Sessions Request: Transaction unique ID: fc10b6f7-e338-4f7c-9654-498360748812, VDA IP: 127.0.0.1
[2020/09/28 12:58:42.1996469] [BrokerAgentAoTracing] [Information] REGISTRATION Ping sent: VDA machine SID S-1-5-21-1111-1354286565-637230989-84109, Broker IP: 10.10.63.2, Load value list: [RuleName=CPU, Load=0],[RuleName=Memory, Load=10000],[RuleName=Disk, Load=0], States:  worker [LoadManagementInitializing] windows maint mode [Enable], PVD data: percent done 100 estimated time left 0 error text , Limits: concurrent logins 2 max sessions 250, Message count 0
[2020/09/28 12:58:42.2854941] [BrokerAgentAoTracing] [Information] REGISTRATION Ping response: VDA machine SID S-1-5-21-1111-1354286565-637230989-84109, Broker IP: 10.10.63.2, Heartbeat period: min 30000 max 00:05:00 update threshold 500, Message count: 0, Image out of date: False
 

The ping sent and ping response log show its already registered. 

 

If the issue still exists, can you open verbose log of vda and jproxy for troubleshooting?

service jproxy all, service ctxjproxy restart

setlog vda all, service ctxvda restart

 

Thanks,

Qian

[Przemyslaw Mantaj]

I de-assigned all Citrix Policies from the delivery group for Linux machines and the state changed from Initializing to Registered and Linux VDA works correctly.