Forum Discussion

tstepnia's avatar
tstepnia
Icon for Altostratus rankAltostratus
Aug 09, 2019

OS upgrade for BIG-IP APM from 12.1.3.1 to 14.1 and all Linux boxes are not able connect to desktop with vmware-view.

 

Problem was caused by OS upgrade for BIG-IP APM from 12.1.3.1 to 14.1.

After installation only Linux clients started to get black screen then disconnection.

 

Was running Fedora 29, now 30.

 

I am in posession of vmware-view logs only.

2019-05-04 07:59:59.608+02:00: vmware-view 30941| rmksContainer(31022): CreateMKSInterface: forcing mount, Remote MKS already present
 
2019-05-04 07:59:59.608+02:00: vmware-view 30941| rmksContainer(31022): OnMountUnmount: (0, 0) 1440 X 810.
 
2019-05-04 08:00:03.417+02:00: vmware-view 30941| rmksContainer(31022): OnDisplayTopologyChanged: monitor 0: left=0, top=0, right=1440, bottom=810

 

 I am not able to connect to desktop using Linux client.

I've tried Horizon View 4.9, 4.10, 5.0, 5.2 versions installed from available bundles following previous uninstallation.

 

Fresh Fedora installation does not help.

Connection from Android tablet works fine - version 4.10.

 

Did anyone face this issue and knows how to solve it?

 

 

Connection logs show:
 
2019-05-02 13:46:54.144+02:00: vmware-view 22919| TaskCombiner: SetResult for CdkGetLaunchItemConnectionTask(DONE).
 
2019-05-02 13:46:55.938+02:00: vmware-view 22919| rmksContainer(23089): CreateMKSInterface: Remote MKS not yet present, queueing CheckForMount
 
2019-05-02 13:46:55.938+02:00: vmware-view 22919| rmksContainer(23089): Caught child exit with status 0x500, requesting container exit
 
2019-05-02 13:46:55.938+02:00: vmware-view 22919| rmksContainer(23089): Remote MKS network connection status changed: DISCONNECTED
 
2019-05-02 13:46:55.938+02:00: vmware-view 22919| rmksContainer(23089): ProcessPollCb: received exit request, shutting down...
 
2019-05-02 13:47:05.939+02:00: vmware-view 22919| rmksContainer(23089): Killing vmware-remotemks child: 5a35
 
2019-05-02 13:47:05.942+02:00: vmware-view 22919| rmksContainer(23089) died.
 
2019-05-02 13:47:05.942+02:00: vmware-view 22919| rmksContainer(23089) exited with status: 5
 
 
 
vmware-mks-2252.log looks interesting:
 
2019-05-03T08:36:35.924+02:00| main| I125: VDPPLUGIN: pcoip_client: connecting to target
 
2019-05-03T08:36:35.924+02:00| main| I125: Peer reported input preferences 0x1.
 
2019-05-03T08:36:35.924+02:00| main| I125: Peer has no preferred mouse mode.
 
2019-05-03T08:36:35.924+02:00| main| I125: Peer reported input capabilities 0x2.
 
2019-05-03T08:36:35.924+02:00| main| I125: Peer supports absolute mouse.
 
2019-05-03T08:36:35.950+02:00| mks| W115: VDPPLUGIN: pcoip_client: disconnect reason code 5: VDPCONNECT_C
 
ONNECTION_LOST
 
2019-05-03T08:36:35.950+02:00| mks| I125: MKSRoleMain: Disconnected from server.
 
2019-05-03T08:36:35.950+02:00| mks| I125: MKSRoleMain: Disconnected from server with error code 5.

 

APM
BIG-IP
security
vmware-viewlinux

4 Replies

Sort By
  • boneyard's avatar
    boneyard
    Icon for MVP rankMVP
    Aug 10, 2019

    probably not the answer you are hoping for but i would advise to contact your f5 partner or f5 support also. you might get lucky with someone experiencing exactly the same, but in general this requires troubleshooting and such which is difficult via forum like this.

     

    you mention an APM change, what change?

     

    which APM version?

     

    did you check the APM client compatibility matrix?

     

    https://techdocs.f5.com/kb/en-us/products/big-ip_apm/manuals/product/apm-clientcompatmatrix-13-0-1.html

    • tstepnia's avatar
      tstepnia
      Icon for Altostratus rankAltostratus
      Aug 13, 2019

      Thanks, here are the details I was able to get:

       

      OS upgrade for BIG-IP APM from 12.1.3.1 to 14.1

       

      • VMware Horizon View 5.2

       

      is on the matrix compatibility list.

      • boneyard's avatar
        boneyard
        Icon for MVP rankMVP
        Aug 13, 2019

        next to a bug, for which you might get lucky someone here encountered exactly the same, but else you will need to go through F5 support

         

        the only thing i can imagine, although weird it would just affect Linux client, is different default SSL ciphers

         

        https://support.f5.com/csp/article/K54125331

        https://support.f5.com/csp/article/K13156

         

        were custom cipher strings used, or the default ones?