VMware Horizon Community
MWigger
Contributor
Contributor

Issues with linux agent installation

Hello,

I try to get a centos 7  machine running with the Linux view agent, but it does not appear in the view server.

When I make a tcpdump and restart the agent, I see that no connection is attempted to the connection server

The values for NAME,HOSTNAME,BROKER,KDC,DOMAIN,BROKERKDC,BROKERDOMAIN are set in the config.

This is in the debug log:

2017-02-01T13:38:28.855Z DEBUG <Script Stdout> [LinuxUtilities] finished MonitorLoginUser

2017-02-01T13:38:28.856Z DEBUG <Script Runner> [LinuxUtilities] process terminated with rc 143, script: /usr/lib/vmware/viewagent/bin/vmMonitorLoginUser.sh MonitorLoginUser

2017-02-01T13:38:28.856Z DEBUG <Script Runner> [LinuxUtilities] Script finished: /usr/lib/vmware/viewagent/bin/vmMonitorLoginUser.sh MonitorLoginUser

2017-02-01T13:38:28.856Z DEBUG <Script Runner> [LinuxUtilities] thread finished...

2017-02-01T13:38:28.858Z DEBUG <Thread-1> [StandaloneAgent] Stopping Sso handler thread

2017-02-01T13:38:28.858Z DEBUG <Thread-1> [StandaloneAgent] Stopping blast server handler

2017-02-01T13:38:28.858Z DEBUG <Thread-1> [StandaloneAgent] Stopping Monitor Console Session Process

2017-02-01T13:38:28.859Z DEBUG <Thread-1> [StandaloneAgent] Stopping Monitor Login User Process

2017-02-01T13:38:28.859Z DEBUG <Thread-1> [StandaloneAgent] Stopping Monitor mksvchanserver Process

2017-02-01T13:38:28.859Z DEBUG <Thread-1> [StandaloneAgent] Stopping Monitor machine id Process

2017-02-01T13:38:28.859Z DEBUG <Thread-1> [StandaloneAgent] Stopping Monitor Host name Process

2017-02-01T13:38:28.860Z DEBUG <FileMonitor for /var/vmware/viewagent/logEvent> [FileMonitor] Interrupted while watching file

2017-02-01T13:38:28.860Z DEBUG <FileMonitor for /var/vmware/view.myuser/screenLockEvent> [FileMonitor] Interrupted while watching file

2017-02-01T13:38:29.527Z DEBUG <main> [StandaloneAgent] Configuring machine

2017-02-01T13:38:29.985Z DEBUG <main> [StandaloneAgentConfig] Current fqdn is mydesktop2.mydomain.net

2017-02-01T13:38:29.990Z DEBUG <main> [StandaloneAgentConfig] Reading customer configuration from /etc/vmware/viewagent-custom.conf

2017-02-01T13:38:29.990Z DEBUG <main> [StandaloneAgentConfig] Set subnet: 10.0.0.0/8

2017-02-01T13:38:29.996Z DEBUG <main> [Utils] Using IP Address 10.16.69.25

2017-02-01T13:38:29.998Z DEBUG <main> [StandaloneAgent] Initialising JMS Certificate Manager from directory /etc/vmware/jms

2017-02-01T13:38:30.017Z DEBUG <main> [StandaloneAgent] Read thumbprint: 7e:3e:fe:e1:66:05:7e:7e:77:ff:c2:f3:f3:72:f5:bd:15:a1:23:c0#SHA_1

2017-02-01T13:38:30.020Z DEBUG <Script Runner> [LinuxUtilities] Running script: /usr/lib/vmware/viewagent/bin/vmMonitorLoginUser.sh MonitorLoginUser

2017-02-01T13:38:30.021Z DEBUG <main> [NetworkMonitor] The broker list is

2017-02-01T13:38:30.023Z DEBUG <NetworkMonitor> [NetworkMonitor] Start running monitor network Thread

2017-02-01T13:38:30.024Z DEBUG <Script Runner> [LinuxUtilities] waiting for process to terminate, script: /usr/lib/vmware/viewagent/bin/vmMonitorLoginUser.sh MonitorLoginUser

2017-02-01T13:38:30.034Z DEBUG <Script Stdout> [LinuxUtilities] vmMonitorLoginUser: start monitor the login user MonitorLoginUser

2017-02-01T13:38:30.037Z DEBUG <Script Stdout> [LinuxUtilities] vmMonitorLoginUser: host name: mydesktop2.mydomain.net, host info: mydesktop2.mydomain.net MonitorLoginUser

2017-02-01T13:38:30.097Z DEBUG <FileMonitor for /var/vmware/viewagent/logEvent> [FileMonitor] logEvent has changed

2017-02-01T13:38:30.097Z DEBUG <FileMonitor for /var/vmware/viewagent/logEvent> [ConsoleSessionHandler] mydesktop2.mydomain.net myuser

2017-02-01T13:38:30.102Z DEBUG <FileMonitor for /var/vmware/viewagent/logEvent> [StandaloneAgent] Console session created for user: myuser, domain: mydesktop2.mydomain.net

any ideas how to proceed?

Best regards,

Marius

Reply
0 Kudos
6 Replies
jtrutwin
Contributor
Contributor

I didn't have any issues setting up View Agent on RHEL7 which should be the same as CentOS - my guess is you have a firewall issue between your desktops and your security/connection servers.

Reply
0 Kudos
MWigger
Contributor
Contributor

Hello thanks for the tip, the firewalld was on

But disabeling did not help, I still dont even see an attempt to connect

Reply
0 Kudos
txiong
VMware Employee
VMware Employee

Hi MWigger,

1. What version are your using?

2. How did you installed Horizon for Linux? Would you please post the command?

3. "The values for NAME,HOSTNAME,BROKER,KDC,DOMAIN,BROKERKDC,BROKERDOMAIN are set in the config" ==> did you manually updated these options?


4. Would you please also post the output of command: vmware-rpc machine.id.get?


Thank you!

Reply
0 Kudos
MWigger
Contributor
Contributor

1. Version 7.0.3

2. ./install_viewagent.sh -b mybroker.mydomain.com -d mydomain.com -u administrator

3. NAME, HOSTNMAE BROKER were set automatically, the remaining where on the default and manually changed

4. I assume you mean vmware-rpctool:

vmware-rpctool machine.id.get

No machine id

Best regards, Marius

Reply
0 Kudos
txiong
VMware Employee
VMware Employee

Thanks for your quick update, Marius.

Your installation command is to register the Linux machine to broker, which means the un-managed VM desktop. Actually, from 7.0.1, Linux Desktop switched to vCenter managed VM desktop. Here is brief steps.

1. Install the Linux Agent with vCenter managed VM mode: sudo ./install_viewagent.sh -A yes

2. Create Linux Desktop Pool on broker Create a Manual Desktop Pool for Linux

Tips:

  1. Linux machine should be configured to resolve broker's FQDN

  2. LinuxVM's vRAM should be configured manually from vSphere client: Virtual Machine Settings for 2D and vSGA Graphics

Please let me know if it works in your env. Thanks.

Reply
0 Kudos
jtrutwin
Contributor
Contributor

FWIW I've found that 64 MB video card RAM seems to be about the minimal setting to have nice smooth full-screen displays for linux desktops in view.  Good luck.

Reply
0 Kudos