Horizon View Client Version 2012-8.1, 2103-8.2 hungs in LogOff Screen

[rohrbachger]

We have since a while Vmware Client 2006-8.0 in use, this works in general fine.

We are trying to update now as we want to upgrade the environment to 2012-8.1

On the windows based clients there is no issue with a new client version. We have tested with the actual thinstation version just pulled, with 8.1 and 8.2. When looging off, the blue logoff screen hungs. ps -A we do see vmware-print-re <defunct)

kill vmware-remotemk ends the task

Can someone give a hint, how we can get this solved?

[Thinstation]

You might need to attach to the task with strace and see what it is trying to do, that it can't.

On Wed, Jul 7, 2021 at 1:02 AM rohrbachger @.***> wrote:

We have since a while Vmware Client 2006-8.0 in use, this works in general fine.

We are trying to update now as we want to upgrade the environment to 2012-8.1

On the windows based clients there is no issue with a new client version. We have tested with the actual thinstation version just pulled, with 8.1 and 8.2. When looging off, the blue logoff screen hungs. ps -A we do see vmware-print-re <defunct)

kill vmware-remotemk ends the task

Can someone give a hint, how we can get this solved?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Thinstation/thinstation/issues/649, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVW47SQIT4WQQAGJ2QC3CDTWQCX5ANCNFSM476DURSQ .

[Thinstation]

Also, try running it in the chroot and see if it works.

On Wed, Jul 7, 2021 at 4:00 AM Donald Cupp @.***> wrote:

You might need to attach to the task with strace and see what it is trying to do, that it can't.

On Wed, Jul 7, 2021 at 1:02 AM rohrbachger @.***> wrote:

We have since a while Vmware Client 2006-8.0 in use, this works in general fine.

We are trying to update now as we want to upgrade the environment to 2012-8.1

On the windows based clients there is no issue with a new client version. We have tested with the actual thinstation version just pulled, with 8.1 and 8.2. When looging off, the blue logoff screen hungs. ps -A we do see vmware-print-re <defunct)

kill vmware-remotemk ends the task

Can someone give a hint, how we can get this solved?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Thinstation/thinstation/issues/649, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVW47SQIT4WQQAGJ2QC3CDTWQCX5ANCNFSM476DURSQ .

[Thinstation]

Is this still an issue with the latest View client?

[rohrbachger]

I will try again. We have some other issues with freezing thinstation in combination with view. This is really hard to debug. It has somehow to do with screen saver. But happens not always, so it is not really to reproduce.. We have tried several options, in most cases it happens on Dell Optiplex 790, but also Lenovo.

I have seen the new horizon client is available, I wiil test with this version and give feedback.

[rohrbachger]

Tested now with latest thinstation version and latest vmware horizon clien 2106.1 The problem when logging off ( hungs in blue windows logoff screen) disappears. In the next week we will rollout this new version to some of our clients, to see if freezing thinstation sometimes will disappear also. This will take a while for testing, so I will close this issue. Nobody else seem to have similar issues.

[rohrbachger]

I switched over to Client 2106.1 . After 2 weeks in production we noticed the same effect like on 2012-81 and 2103-8.2. The session works fine, but after logoff the session is not closed completely. On the broker server it is ended. I have tested already and disabled all unnecessary options like printer redirect, USB , scannner etc. This has not helped. On ubuntu this client version works fine. I have tried with strace to analyse, but never used it before. What option might give a good log file? I used strace -o test.log -f -p Any hint what to do in detail?

[Thinstation]

It might be my kernel+bug in Horizon. I have some of the grsecurity options enabled, like zero on free. Use after free bugs are tricky to diagnose. I’ll put together a test kernel for you.

On Mon, Oct 18, 2021 at 2:35 AM rohrbachger @.***> wrote:

I switched over to Client 2106.1 . After 2 weeks in production we noticed the same effect like on 2012-81 and 2103-8.2. The session works fine, but after logoff the session is not closed completely. On the broker server it is ended. I have tested already and disabled all unnecessary options like printer redirect, USB , scannner etc. This has not helped. On ubuntu this client version works fine. I have tried with strace to analyse, but never used it before. What option might give a good log file? I used strace -o test.log -f -p Any hint what to do in detail?

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/Thinstation/thinstation/issues/649#issuecomment-945586120, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVW47S7QB5QKYVG55K2JV3UHPS4JANCNFSM476DURSQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[Doncuppjr]

I just pushed an alt kernel to my repo. Pull, unwind and build with --kernel NGR , as in Non-GRSecurity.

[rohrbachger]

I tried this, uname -a shows 5.10.70TS_NGR. So I guess I did it right. With Vmware horizon client 2012 8.1 and with VMware-Horizon-Client-2106.1-8.3.1-18435609.x64.bundle. Exactly the same behaviour, the vm session stays in logoff screen and never ends. There are two process, vmware-remotemk and vmware-print-re. When trying logoff vmware-print-re goes to -defunct- I have tried already disabling the feature printer redirection in the install script, but this process is still created. On my ubuntu a process vmware-print-re is never created, when I disable printer redirection and other features. I can not say, if this printer redirection is causing the issue. But as we do not need this feature I will try to find out why this process is created. Might be a problem in the package.

[rohrbachger]

In he script I have disabled the features, but during generating TS it shows as installed. I do not understand really the install script. So will try to figure out what it is doing.

!/bin/bash

gzname=basename $1 INSTALLDIR=./packages/vmview

components="\ --set-setting vmware-horizon-smartcard smartcardEnable no \ --set-setting vmware-horizon-rtav rtavEnable no \ --set-setting vmware-horizon-usb usbEnable no \ --set-setting vmware-horizon-virtual-printing tpEnable no \ --set-setting vmware-horizon-tsdr tsdrEnable no \ --set-setting vmware-horizon-mmr mmrEnable no \ --set-setting vmware-horizon-scannerclient scannerEnable no \ --set-setting vmware-horizon-media-provider mediaproviderEnable no"

TS-LOG.txt

[Doncuppjr]

It will go through each sub-installer, but only the essential ones actually installed anything.

Sent from Yahoo Mail for iPhone

On Tuesday, October 19, 2021, 2:48 AM, rohrbachger @.***> wrote:

In he script I have disabled the features, but during generating TS it shows as installed. I do not understand really the install script. So will try to figure out what it is doing.

!/bin/bash

gzname=basename $1 INSTALLDIR=./packages/vmview

components=" --set-setting vmware-horizon-smartcard smartcardEnable no --set-setting vmware-horizon-rtav rtavEnable no --set-setting vmware-horizon-usb usbEnable no --set-setting vmware-horizon-virtual-printing tpEnable no --set-setting vmware-horizon-tsdr tsdrEnable no --set-setting vmware-horizon-mmr mmrEnable no --set-setting vmware-horizon-scannerclient scannerEnable no --set-setting vmware-horizon-media-provider mediaproviderEnable no"

TS-LOG.txt

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[Doncuppjr]

Next test.....

I added a port that will download the ubuntu kernel. pull, no clean is required. prt-get install ubuntu-kernel build --kernel 5.8.0-63-generic --allmodules

[rohrbachger]

build done succesful, but got a kernel panic during boot. VFS: cannot open root device ram0 or unknown-block unable to mount root fs unknown block(0,0)

I'm using an ISO and boot with iPXE, the same procedure I do with TS.

[Doncuppjr]

Hmm. make initramfs gzip, and drop overlay.

[rohrbachger]

Now I lost you. Where I have to change this?

[Doncuppjr]

in build.conf. drop the overlay package, and change param initramfs to gzip

[rohrbachger]

Got it, I'm̀ using my old build.conf, that's why I did not found the entry. param initrdcmd "gzip"

or param initramfs "gzip"

[rohrbachger]

Tried both paramerers. Different messages loading vmlinux ok load initrd ok

pivot_root failed to chnage roof from . to mnt/union/oldroot invalid argument /lib/systemd/systemd error whil load laged libraries libkmod.so.2 kernel panic

[Doncuppjr]

Sorry, initrdcmd gzip is correct.

You don't want to pivot. Whatever package is pivoting, comment it out.

[Doncuppjr]

Oh, and the ubuntu kernel is very noisy and slow to boot. Maybe wait a minute.

[rohrbachger]

My mistake, some lines above was still initrdcmd=squashfs . I removed and did a build with build --kernel 5.8.0-63-generic --allmodules Different screen, still kernel panic. Trying to unpack rootfs image as initramfs initramfs unpacking failed.

My test system is a lenovo M715Q with 8GB RAM. ( I took a video to be able to read the error message) I disabled splash and changed bootverbosity to 63.

[Doncuppjr]

also make sure that package overlayfs is disabled.

[rohrbachger]

package overlayfs is disabled I build new, the same initramfs unpacking failed. write error

Here my build.conf build.txt

[Doncuppjr]

How big is the image?

[rohrbachger]

685MB is the ISO, i used already larger.

[Thinstation]

How long did you give it to boot?

On Wed, Oct 20, 2021 at 7:35 AM rohrbachger @.***> wrote:

685MB is the ISO, i used already larger.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/Thinstation/thinstation/issues/649#issuecomment-947730029, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVW47WNQYBW5MDXH2B25DDUH3HTNANCNFSM476DURSQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rohrbachger]

It is coming up with the kernel error after some seconds, it does not take long. I get all messages on the screen and are using my mobile to take the video. I can 't read that fast.

[rohrbachger]

I'm booting the ISO with iPXE, so it does not take long to get the image. It is http no tftp.

[Doncuppjr]

Keep waiting. I had very noisy boots and kernel complaints, but eventually it did boot.

[rohrbachger]

got it, I thought with kernel panic it is dead. I will wait.

The last message on screen is end Kernel panic not syncing: Attempted to kill init! exit code 0x00007f00

[rohrbachger]

Not booted after a long time.

[Thinstation]

Can you try with smaller images in the 200-300 Mb range?

On Wed, Oct 20, 2021 at 9:21 AM rohrbachger @.***> wrote:

Not booted after a long time.

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/Thinstation/thinstation/issues/649#issuecomment-947827923, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVW47QMKVPVVBJ2Q57GTLDUH3T7NANCNFSM476DURSQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rohrbachger]

You were right, it has to do somehow with the size. I removed chrome and view, and it boots. And it is booting fast, so I can not really see a difference. With vmview package I was above 500MB, that did not boot. Kernel panic. I will try now to remove some other packages, so that I come under 500MB Is there maybe a ram disk size I need to set larger. The machine has enough ram. At least I want to be able to the test view behaviour.

[rohrbachger]

Without View the size is about 400MB, with Vmware it is approx 550MB. Iḿ not able to get it smaller, I removed already fonts and eveything what is needed.

I need to set the parameter allfirmware, otherwise I get a black screen only. This is using a lot space , without allfirmware are with vmclient on 450MB.

How can I figure out which firmware is needed and where can I reduce it. For a test I would just delete the files.

[rohrbachger]

Finally I found a way for my test. The image is booting fine with the special ubuntu kernel, also fast. Running vmview works, but exactly the same behaviour when ending the view session like with the ts kernel. Session hangs at the end in Logoff. I think this might be an evidence, that not the kernel is the issue. The view package is really tricky done, the guy that did it made a good job. But probably with a newer client version there is something to change.

[Doncuppjr]

I was able to get a bootable image with view and 8g of ram. 

On Thursday, October 21, 2021, 05:30:03 AM PDT, rohrbachger @.***> wrote:

Finally I found a way for my test. The image is booting fine with the special ubuntu kernel, also fast. Running vmview works, but exactly the same behaviour when ending the view session like with the ts kernel. Session hangs at the end in Logoff. I think this might be an evidence, that not the kernel is the issue. The view package is really tricky done, the guy that did it made a good job. But probably with a newer client version there is something to change.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[Doncuppjr]

Is cups in the build?

On Thursday, October 21, 2021, 07:49:12 AM PDT, Don Cupp @.***> wrote:

I was able to get a bootable image with view and 8g of ram. 

On Thursday, October 21, 2021, 05:30:03 AM PDT, rohrbachger @.***> wrote:

Finally I found a way for my test. The image is booting fine with the special ubuntu kernel, also fast. Running vmview works, but exactly the same behaviour when ending the view session like with the ts kernel. Session hangs at the end in Logoff. I think this might be an evidence, that not the kernel is the issue. The view package is really tricky done, the guy that did it made a good job. But probably with a newer client version there is something to change.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[rohrbachger]

No, but I will test it. Vmware switched over the printing with newer versions.

[rohrbachger]

Cups installed, vmview actual version, standard TS. Still he same, hangs on exit. Changes the view client was printing in general and teams vmware-horizon-teams-optimization This is standard and can not disabled or uninstalled.

[Doncuppjr]

Okay, on an Ubuntu host, clone the chroot and unwind it. Run the vmware installer within the chroot, don't worry about build for the moment. Run the client in the chroot and see what happens with the log off.

[rohrbachger]

I'm on a Trip, will continue sunday evening

[Doncuppjr]

do a ./build --removeall, then remove these files vmview/build/extra/etc/skel/.thnuclnt/thnuclnt.conf vmview/build/extra/etc/systemd/system/multi-user.target.wants/thnuclnt.service vmview/build/extra/etc/systemd/system/thnuclnt.service vmview/build/extra/lib/vmware/view/virtualPrinting/scripts/initscript-virtual-printing.sh then make a new build.

[rohrbachger]

I cloned again, to make sure that everything is original. I removed the files for the printing. Still no change, same behaviour, session hangs in logoff. I removed then also the usb redirection and the two scanner services. Still no change

Still there is a task vmware-print-re with defunct in ps. Thatś probably the new printing system what is included.

[Doncuppjr]

Try installing and running in the chroot on an Ubuntu host.

[rohrbachger]

(vmware-view:4781): Gtk-WARNING **: 17:48:46.512: cannot open display: :0

What I have to do to get x running in the chroot. Can that work? Or is it better to run the thinstation development environment. I remember I used it a while ago. Thee is x already running.

[Doncuppjr]

programs that need X should be able to use the display. I'm not having any issues on F35

[Thinstation]

I pushed a fix for ubuntu

[rohrbachger]

I tried on a new ubuntu 20.04 machine and cloned from github TS I can install view client in the chroot, but already there comes a message no gui Message wenn I start vmware-view is warning, cannot display :0 On the ubuntu there is already X running, so maybe this is a problem?

[Thinstation]

I pushed a fix that should work on 21. Not sure about 20

On Wed, Oct 27, 2021 at 5:53 AM rohrbachger @.***> wrote:

I tried on a new ubuntu 20.04 machine and cloned from github TS I can install view client in the chroot, but already there comes a message no gui Message wenn I start vmware-view is warning, cannot display :0 On the ubuntu there is already X running, so maybe this is a problem?

— You are receiving this because you commented.

Reply to this email directly, view it on GitHub https://github.com/Thinstation/thinstation/issues/649#issuecomment-952896043, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAVW47U7SHFETA33UY22M4TUI775XANCNFSM476DURSQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

[rohrbachger]

I will update to 21.04