I installed latest centos release 7.5 on Horizon 7.4 - with the agent, however I had troubles connecting to the VM through all protocols (HTML , Client)
I flushed iptables on the VM with no help.
note that Windows 10 VMs are working and Ubuntu 16.04 is working too through html.
here is a log:
from HTML access: Failed to resolve proxying route for request
Vmware agent debug log file from the VM:
2018-06-28T13:52:40.466Z INFO <pool-2-thread-2> [StandaloneAgent] Start session for user: sitani
2018-06-28T13:52:40.466Z INFO <pool-2-thread-2> [StandaloneAgent] Creating new session for user:sitani
2018-06-28T13:52:40.466Z INFO <pool-2-thread-2> [StandaloneAgent] Starting SSO service
2018-06-28T13:52:40.466Z DEBUG <pool-2-thread-2> [StandaloneAgent] Stopping Sso handler thread
2018-06-28T13:52:40.467Z DEBUG <pool-2-thread-2> [SsoHandler] Create SsoHanlder for CentOS
2018-06-28T13:52:40.477Z DEBUG <pool-2-thread-2> [StandaloneAgent] Stopping Monitor mksvchanserver Process
2018-06-28T13:52:40.477Z INFO <pool-2-thread-2> [StandaloneAgent] Destroy the monitor mksvchanserver sub process.
2018-06-28T13:52:40.477Z INFO <pool-2-thread-2> [StandaloneAgent] Stop clipboard script: /usr/lib/vmware/viewagent/bin/StopClipboard.sh
2018-06-28T13:52:40.478Z DEBUG <SSOThread> [SsoHandler] Sso handler thread running
2018-06-28T13:52:40.479Z DEBUG <Script Runner> [LinuxUtilities] Running script: /usr/lib/vmware/viewagent/bin/StopClipboard.sh
2018-06-28T13:52:40.483Z DEBUG <Script Runner> [LinuxUtilities] waiting for process to terminate, script: /usr/lib/vmware/viewagent/bin/StopClipboard.sh
2018-06-28T13:52:40.545Z DEBUG <Script Stdout> [LinuxUtilities] Kill the running StartClipboard.sh: 30009
2018-06-28T13:52:41.074Z DEBUG <Script Runner> [LinuxUtilities] process terminated with rc 0, script: /usr/lib/vmware/viewagent/bin/StopClipboard.sh
2018-06-28T13:52:41.074Z DEBUG <Script Runner> [LinuxUtilities] Script finished: /usr/lib/vmware/viewagent/bin/StopClipboard.sh
2018-06-28T13:52:41.075Z DEBUG <Script Stdout> [LinuxUtilities] finished
2018-06-28T13:52:41.075Z DEBUG <Script Runner> [LinuxUtilities] thread finished...
2018-06-28T13:52:41.075Z INFO <pool-2-thread-2> [StandaloneAgent] Stop clipboard: /usr/lib/vmware/viewagent/bin/StopClipboard.sh
2018-06-28T13:52:41.075Z DEBUG <pool-2-thread-2> [StandaloneAgent] Attempting to start Blast Server
2018-06-28T13:52:41.075Z WARN <pool-2-thread-2> [DisplayTopology] Displays.Topology not present in client info
2018-06-28T13:52:41.075Z DEBUG <pool-2-thread-2> [StandaloneAgent] Client OS type is not supported.
2018-06-28T13:52:41.076Z DEBUG <pool-2-thread-2> [BlastHandler] The blast server will listen on the port: 37627
2018-06-28T13:52:41.076Z DEBUG <pool-2-thread-2> [BlastHandler] Start blast server with timeout: 20000 ms
2018-06-28T13:52:41.080Z DEBUG <Script Runner> [LinuxUtilities] Running script: /usr/lib/vmware/viewagent/bin/StartSession.sh
2018-06-28T13:52:41.085Z DEBUG <Script Runner> [LinuxUtilities] waiting for process to terminate, script: /usr/lib/vmware/viewagent/bin/StartSession.sh
2018-06-28T13:52:41.472Z DEBUG <Script Runner> [LinuxUtilities] process terminated with rc 0, script: /usr/lib/vmware/viewagent/bin/StartSession.sh
2018-06-28T13:52:41.472Z DEBUG <Script Runner> [LinuxUtilities] Script finished: /usr/lib/vmware/viewagent/bin/StartSession.sh
2018-06-28T13:52:41.741Z DEBUG <MKSControlIPCThread> [AsynSocketClient] Connecting to mksVNCServer/127.0.0.1:37627
2018-06-28T13:52:41.742Z DEBUG <MKSControlIPCThread> [AsynSocketClient] Connected to mksVNCServer/127.0.0.1:37627
2018-06-28T13:52:41.742Z DEBUG <MKSControlIPCThread> [AsynSocketClient] mks control socket send 48 bytes data
2018-06-28T13:52:41.743Z DEBUG <MKSControlIPCThread> [AsynSocketClient] mks control socket recv 96 bytes data
2018-06-28T13:52:41.743Z INFO <MKSControlIPCThread> [MKSControlCmd] Undefined mks control command type 30
2018-06-28T13:52:41.743Z INFO <MKSControlIPCThread> [MKSControlCmd] Unknown command type 15
2018-06-28T13:52:41.743Z INFO <MKSControlIPCThread> [MKSControlCmd] The unknown MKS control command type: 15
2018-06-28T13:52:41.743Z INFO <MKSControlIPCThread> [MKSControlCmd] Undefined mks control command type 25
2018-06-28T13:52:41.743Z INFO <MKSControlIPCThread> [MKSControlCmd] Unknown command type 15
2018-06-28T13:52:41.743Z INFO <MKSControlIPCThread> [MKSControlCmd] The unknown MKS control command type: 15
2018-06-28T13:52:41.743Z DEBUG <MKSControlIPCThread> [BlastHandler] Recv notifyConnectSuccess message
2018-06-28T13:52:41.743Z INFO <MKSControlIPCThread> [StandaloneAgent] Blast Server connection established
2018-06-28T13:52:41.743Z DEBUG <MKSControlIPCThread> [AsynSocketClient] mks control socket send 12 bytes data
2018-06-28T13:52:41.745Z DEBUG <pool-2-thread-2> [StandaloneAgent] Blast Server started and agent connected
2018-06-28T13:52:41.745Z DEBUG <pool-2-thread-2> [BlastHandler] Revoking vauth token: JJNSF-***-AGTKQ
2018-06-28T13:52:41.746Z DEBUG <pool-2-thread-2> [BlastHandler] Adding vauth token: IJPGI-***-U6MBI
2018-06-28T13:52:41.746Z DEBUG <pool-2-thread-2> [BlastHandler] Sending add vauth token request
2018-06-28T13:52:41.746Z DEBUG <pool-2-thread-2> [BlastHandler] Sending ping to acknowledge vauth token request
2018-06-28T13:52:41.746Z DEBUG <pool-2-thread-2> [BlastHandler] Waiting for ping response with seqNum 13
2018-06-28T13:52:41.746Z DEBUG <MKSControlIPCThread> [AsynSocketClient] mks control socket recv 12 bytes data
2018-06-28T13:52:41.746Z DEBUG <MKSControlIPCThread> [BlastHandler] Recv ping response message with 12 seqNum
2018-06-28T13:52:41.746Z DEBUG <MKSControlIPCThread> [AsynSocketClient] mks control socket send 49 bytes data
2018-06-28T13:52:41.746Z DEBUG <MKSControlIPCThread> [AsynSocketClient] mks control socket send 49 bytes data
2018-06-28T13:52:41.746Z DEBUG <MKSControlIPCThread> [AsynSocketClient] mks control socket send 12 bytes data
2018-06-28T13:52:41.793Z DEBUG <MKSControlIPCThread> [AsynSocketClient] mks control socket recv 12 bytes data
2018-06-28T13:52:41.793Z DEBUG <MKSControlIPCThread> [BlastHandler] Recv ping response message with 13 seqNum
2018-06-28T13:52:41.793Z DEBUG <pool-2-thread-2> [BlastHandler] Ping response received to acknowledge vauth token request
2018-06-28T13:52:41.793Z DEBUG <pool-2-thread-2> [ComponentResponse] Reponse directed to:ID:/127.0.0.1/8689567780313935343/90062/0
2018-06-28T13:52:41.793Z DEBUG <pool-2-thread-2> [ComponentResponse] Message is <?xml version="1.0"?><TERMINALRESPONSE> <ID>4482df8e:1641d66c7e5:-366d</ID> <SERVERDN>cn=7ffc2e5b-b409-47f7-9a9c-9bce8f488eb1,ou=servers,dc=vdi,dc=vmware,dc=int</SERVERDN> <SERVERPOOLDN>cn=research_dedicated,ou=server groups,dc=vdi,dc=vmware,dc=int</SERVERPOOLDN> <SERVERDNSNAME>head1-msfea</SERVERDNSNAME> <DYNAMICIPADDRESS>192.168.122.1</DYNAMICIPADDRESS> <FRAMEWORKCHANNELTICKET>XXXXXXXX</FRAMEWORKCHANNELTICKET> <FRAMEWORKSSLALGORITHM>thisIsAframeworkSSLAlgo</FRAMEWORKSSLALGORITHM> <FRAMEWORKSSLTHUMBPRINT>thisIsAframeworkThumbprint</FRAMEWORKSSLTHUMBPRINT> <TICKET>XXXXXXXX</TICKET> <PROTOCOL> <NAME>BLAST</NAME> <STATUS>ready</STATUS> <PORT>22443</PORT> <HOST>192.168.122.1</HOST> <TOKEN>XXXXXXXX</TOKEN> </PROTOCOL></TERMINALRESPONSE>
2018-06-28T13:52:41.794Z INFO <pool-2-thread-2> [StandaloneAgent] -----SVI State: false USE SVI: false
2018-06-28T13:52:41.794Z DEBUG <pool-2-thread-2> [ComponentResponse] Message is PENDING
2018-06-28T13:52:41.794Z DEBUG <pool-2-thread-2> [JMSHandler] Sending event: AGENT_PENDING
2018-06-28T13:52:41.797Z DEBUG <pool-2-thread-3> [TopicMessageResponder] Response sent.
2018-06-28T13:52:41.798Z DEBUG <pool-2-thread-4> [EventPublishingManager] Checking for message to publish.
2018-06-28T13:52:41.801Z DEBUG <pool-2-thread-3> [AbstractTopicPublishingManager] Message published.
2018-06-28T13:52:41.801Z INFO <pool-2-thread-2> [StandaloneAgent] Start clipboard: /usr/lib/vmware/viewagent/bin/StartClipboard.sh
2018-06-28T13:52:41.801Z DEBUG <pool-2-thread-2> [StandaloneAgent] Starting Monitor Login User Process
2018-06-28T13:52:41.812Z DEBUG <Script Runner> [LinuxUtilities] Running script: /usr/lib/vmware/viewagent/bin/StartClipboard.sh
2018-06-28T13:52:41.826Z DEBUG <pool-2-thread-2> [StandaloneAgent] The usb feature isn't installed
2018-06-28T13:52:41.829Z INFO <pool-2-thread-2> [StandaloneAgent] Clean log: [/usr/lib/vmware/viewagent/bin/CleanupLogFiles.sh, -c, -1]
2018-06-28T13:52:41.829Z DEBUG <pool-2-thread-2> [SessionTimer] starting PENDING_SESSION timer 11 for head1-msfea
2018-06-28T13:52:41.831Z DEBUG <Script Runner> [LinuxUtilities] Running script: /usr/lib/vmware/viewagent/bin/CleanupLogFiles.sh
2018-06-28T13:52:41.861Z DEBUG <Script Runner> [LinuxUtilities] waiting for process to terminate, script: /usr/lib/vmware/viewagent/bin/StartClipboard.sh
2018-06-28T13:52:41.893Z DEBUG <Script Stdout> [LinuxUtilities] StartClipboard.sh pid is: 14445
2018-06-28T13:52:41.895Z DEBUG <Script Runner> [LinuxUtilities] waiting for process to terminate, script: /usr/lib/vmware/viewagent/bin/CleanupLogFiles.sh
2018-06-28T13:52:41.895Z DEBUG <Script Runner> [LinuxUtilities] process terminated with rc 0, script: /usr/lib/vmware/viewagent/bin/CleanupLogFiles.sh
2018-06-28T13:52:41.895Z DEBUG <Script Runner> [LinuxUtilities] Script finished: /usr/lib/vmware/viewagent/bin/CleanupLogFiles.sh
2018-06-28T13:52:41.898Z DEBUG <Script Runner> [LinuxUtilities] thread finished...
2018-06-28T13:52:41.899Z DEBUG <Script Stdout> [LinuxUtilities] finished
2018-06-28T13:52:54.960Z DEBUG <FileMonitor for /var/vmware/viewagent/machineId> [FileMonitor] machineId has changed
2018-06-28T13:52:54.961Z INFO <updateMachineIdImpl> [UpdateMachineIdHandler] Starting update machine id thread.
2018-06-28T13:52:54.961Z DEBUG <updateMachineIdImpl> [UpdateMachineIdHandler] Getting the machine id from file: vdi.broker.emptySessionTimeout=1;vdi.broker.useSysprep=0;vdi.broker.brokers=horizon-srv.win2k.aub.edu.lb ;vdi.broker.agentPrivateKey=XXXX;vdi.broker.asyncSessionSeconds=150;vdi.broker.agentIdentity=agent/7ffc2e5b-b409-47f7-9a9c-9bce8f488eb1;vdi.broker.useSvi=0;vdi.broker.agentPrivateKeyHash=wY48V95vEOsArsym4zQFkw==;vdi.broker.singleuse=0;vdi.broker.msMode=ENHANCED;vdi.broker.disconnecttimeout=0;vdi.broker.emptySessionLogoff=0;vdi.broker.singleuse2=0;vdi.broker.brokerPublicKey=MIHwMIGoBgcqhkjOOAQBMIGcAkEA/KaCzo4Syrom78z3EQ5SbbB4sF7ey80etKII864WF64B81uRpH5t9jQTxeEu0ImbzRMqzVDZkVG9xD7nN1kuFwIVAJYu3cw2nLqOuyYO5rahJtk0bjjFAkBnhHGyepz0TukaScUUfbGpqvJE8FpDTWSGkx0tFCcbnjUDC3H9c9oXkGmzLik1Yw4cIGI1TQ2iCmxBblC+eUykA0MAAkARp6jRYS1GZ/Ynpwh83v45ApE+0mMARbSC0H9JA6CQFSNKK7bArQZ+V5FJhLiC/opR0YUb9AjAp+hFE2A7DN28;vdi.broker.poolDn=cn=research_dedicated,ou=server groups,dc=vdi,dc=vmware,dc=int;vdi.broker.itemDn=cn=7ffc2e5b-b409-47f7-9a9c-9bce8f488eb1,ou=servers,dc=vdi,dc=vmware,dc=int;vdi.broker.preLaunchSessionTimeout=10;vdi.broker.dedicatedPool=1;vdi.broker.brokerPublicKeyHash=s8/wYVSl/e+pJMt6I4+zCQ==
2018-06-28T13:52:54.961Z INFO <updateMachineIdImpl> [StandaloneAgent] Machine id has not changed, update rejected.
any ideas?
thanks!
Hi Saaditani,
Checking ifconfig.txt, there are two ip address configured at this CentOS, could you please configure "Subnet=192.168.137.0/24" at /etc/vmware/viewagent-custom.conf, then restart viewagent service and have a try?
Regards,
Yu
Hi Saaditani,
1. Horizon 7.4 does not officially support CentOS 7.5
2. From the log, BlastServer fails to start due to timeout.
would you please upload the agent DCT bundle? Thanks.
Thank you, we are looking into the logs and will update to you later.
Hi Saaditani,
Checking ifconfig.txt, there are two ip address configured at this CentOS, could you please configure "Subnet=192.168.137.0/24" at /etc/vmware/viewagent-custom.conf, then restart viewagent service and have a try?
Regards,
Yu
Thank you Chenyu it worked, as I added the subnet line!
this is mandatory for every VM after installing the agent or only for centos 7.5?
I appreciate your help mate!
It applied to all VMs, not only CentOS7.5. But only applied to VM which has multiple ip addresses configured.
When installing Linux agent, there shall have prompt "Warning: Multiple networks detected ! You can set the option Subnet in /etc/vmware/viewagent-custom.conf to select the correct IP Address for the Horizon Agent" at the console, when your VM has multiple ip address.
For those VMs only have one ip address, it's no needed.