VMware Horizon Community
edevon
Contributor
Contributor

Horizon refuses to connect

Hi, newbie here.  I've installed Horizon 4.10 on my CentOS 7 PC, and I can successfully authenticate with my employer's remote setup.  But when I try to open a session, it exits after about one second.  (The first time I connected, I did get a blue screen saying that things were being set up, but this exited after some 10s of seconds.  On all subsequent attempts, the blue screen just flashes up and disappears.)  No error message is displayed.

I have found a collection of log files in /tmp/vmware-ed.  Of these, one whose name begins vmware-mks looks relevant.  It contains repeated entries of:

SSLCheckLockingCallback: locking callback overwritten! Expected 56040DE2A660, saw 7FD0D020A280

Then it has entries of:

E105: PANIC: Loop on signal 4.

...

E105: PANIC: Unexpected signal: 4.

E105: Panic loop

...accompanied by lots of stack trace data. 

I have also tried this from Debian 10, with the same result.

Any idea how I can start to diagnose this?

Reply
0 Kudos
6 Replies
NathanosBlightc
Commander
Commander

Hi

Can I ask you why you choose this very old version of VMware view 4.1? On that time it was not even in the Horizon product family :smileygrin:

There is many improvements in newer versions about client/desktop connectivity, protocols, agent status in desktop pool VMs and etc...

Please mark my comment as the Correct Answer if this solution resolved your problem
Reply
0 Kudos
edevon
Contributor
Contributor

Hi Amin, I did not claim to be trying to use version 4.1.  You will see that I say "4.10".  This was the latest version then offered by VMware a week or so ago.  Anyway, your message prompted me to recheck the latest version offered, and I saw that this was now 5.1.0.  I installed this ... and got exactly the same failure, in both CentOS and Debian.  So still at square one I'm afraid. 

Reply
0 Kudos
sjesse
Leadership
Leadership

You should contact your employers helpdesk, they have logs on the server side that may help, and may already be aware of the issue

Reply
0 Kudos
edevon
Contributor
Contributor

Thanks sjesse, that's a good suggestion.  I was intending to do this next Monday in any case, when I am back in the office.  I'll update this thread with anything useful that comes out of that. 

Reply
0 Kudos
NathanosBlightc
Commander
Commander

Did you check horizon Agent is successfully setup on your desktops and are they connected to the horizon server on TCP port 4001 / 4002 ?

check it out with netstat command.

and also check status of TCP / UDP 4172 for PCoIP ...

Please mark my comment as the Correct Answer if this solution resolved your problem
Reply
0 Kudos
vSeanWatson
Contributor
Contributor

When I saw 4.10 I actually looked at the post date. Please install a newer version and test once more. You could also use VMware Workstation to set up a lab to gain some experience.

Reply
0 Kudos