ggt-pcs

[ggt-pcs]

The problem persists when using point b) “Create a new virtual desktop”

As far as the H264 issue is concerned, it seems to work with resolutions up to 1920 × 1080.

We now have an acceptable “working environment” (in terms of responsiveness). Can you confirm that an NVIDIA Kepler based GPU would allow H264 with resolutions > 1920 × 1080 ?

But the one minute lag when connecting to Server-A as well as non-working “user elevation” are still a problem.

One more question: Is the forum the “web based” support that subscribers of NoMachine Workstation are entitled to? If yes, I must point of that it is a little bit frustrating that I get an eMail about the post that I wrote myself but not about your or anybody else’s reply.

have a nice weekend.

[ggt-pcs]

Hi Kroy,

About point v) – is the same situation taking place when you try to “Create a new virtual session”?

Sorry, maybe I’m blind today but there is no option “Create a new virtual session” ?!

As far as I see in “NoMachine Workstation Editon” there are the following options:

a) Physical Desktop

b) Create a new desktop or custom session -> Create a new Virtual Desktop

c) Create a new desktop or custom session -> Create a new custom session -> run cmd floating window

d) Create a new desktop or custom session -> Create a new custom session -> run cmd virtual desktop

Which option do you want me to try?

Note: We have purchased a subscription for 2 x “nomachine-workstation-5.3.9-8.x86_64” running on those servers.

PS: Any reason that I get informed via email about new posts from *me* but not from you or anybody else? This seems very strange!

[ggt-pcs]

Hi, this is OP:

I have debugged quit a lot and have some information to share and some problems still remaining.

i) Information about physical setup: Two DELL Servers R720 running RHEL 7.4. Both servers are connected to a Raritan KVM switch and a Raritan rackmounted monitor.

ii) There was a problem with the screen resolution if the server was restarted while not connected to the monitor. Screen resolution was way off. This problem was solved by using xrandr and adding the modelines to a config file in /etc/X11/xorg.conf.d.

iii) After rebooting both servers and verifying that they have full HD resolution regardless of their connection state to the monitor, NoMachine NX was running much more stable.

iv) I also uninstalled and reinstalled the package nomachine-workstation-5.3.9-8.x86_64 on both servers.

v) Now, when logging on to server-A after choosing “Create a new desktop or custom session” -> “Create a new custom session” -> “Run the default X client script on the server” + “Run the command in a virtual desktop”  and the display “Creating a new custom session” I see a black screen for aprox. 60 seconds with a popup from NX in the upper right corner “User a_garrth connected”. After aprox. 60 seconds the virtual session is displayed and I have the problem stated above (no user name displayed in Logout dialogue, unable to perform elevation (cannot create users)..

vi) during the same on server-B until “and the display “Creating a new custom session” I get the virtual session after aprox. 7 seconds and my name is displayed under “Logoff” as well as user elevation works.

 

BTW: I had rather poor performance in NX (not much better then VNC) because the machine running the NX client is also a DELL server without a dedicated GPU. After googleing I found the notice that I should copy ffmpeg into the program directory of NX Client. Now the performance has really improved — however I’m still stuck with VP8 instead of H.264 even though ffmpeg is installed on the client and NoMachine Workstation should include H.264 encoder.

Any thought about this? Will try to install a dedicated GPU on that server next week to see if this helps.

Any help / tips about solving the user elevation problem on server-A would be appreciated.

kind regards,

ggt-pcs

[ggt-pcs]

Forgot to attach the .xsession-errors. Please find output below:

 

$ cat .xsession-errors

xrandr: Failed to get size of gamma for output default

xrandr: Failed to get size of gamma for output default

xrandr: cannot find output “VGA-0”

xrandr: Failed to get size of gamma for output default

warning: output VGA-0 not found; ignoring

gnome-session-is-accelerated: No composite extension.

gnome-session-check-accelerated: Helper exited with code 256

gnome-session-is-accelerated: No composite extension.

gnome-session-check-accelerated: Helper exited with code 256

 

** (process:44883): WARNING **: software acceleration check failed: Child process exited with code 1

 

[ggt-pcs]

Logs have been sent with the following subject “NoMachine issue “Suddenly unable to “create a new desktop or custom session”  #15474 — requested logs”

[ggt-pcs]

kroy wrote:

Can you point to exactly which option in nxplayer you used during the creation of a new custom session that you have possibility to activate “unlock” button inside?

I’m sorry but currently I cannot accommodate your request since I am unable to create a custom session. This was the original reason for opening this topic. If you can show me how to get it working again (“create a new session”) I’ll be happy to provide you with any debug information you need.

 

 

[ggt-pcs]

Hi,

It’s not an issue. User which is not in the sudo group shouldn’t be allowed to change system settings. Are you sure that custom session was ran as user which wasn’t belong to sudo group? If yes – can you paste here command which was executed to start that custom session?

Both sessions were run as the user “a_garrth” as you can see in attached screenshots. a_garrth is member of the group “wheel”, which, in turn, has sudo privileges.
I’m not sure I get what you mean by ” can you paste here command which was executed to start that custom session?” Since the custom session will not start. Where would I find this information?

Can you paste here output of command:

grep DefaultXSession /usr/NX/etc/node.cfg
DefaultXSession "/etc/X11/xinit/Xsession default"

Attachments:

1. 

   RHEL_NX_physical_desktop.png
   

2. 

   RHEL_NX_virtual_desktop.png
   

[ggt-pcs]

Hi,

• we’re using the RHEL default Desktop Environment (gnome-desktop3-3.14.2-2.el7.x86_64)
• creating a “new virtual desktop” works but there seems to be the issue that “user elevation” does not work. When opening Settings -> Users I cannot activate the “unlock” button (ref. attachment “RHEL_NX_User__not_unlockable.png”)
  When opening a new custom session (in client resolution) or connecting to physical desktop, this is possible. (ref. attachment RHEL_NX_User_unlockable.png from connection to physical desktop)
•  grep -E “DefaultDesktopCommand|DefaultXCommand” /usr/NX/etc/node.cfg
  DefaultDesktopCommand “/etc/gdm/Xsession ‘gnome-session –session=gnome'”

Hope this helps 🙂

Attachments:

1. 

   RHEL_NX_User__not_unlockable.png
   

2. 

   RHEL_NX_User_unlockable.png
   

[Author]

Posts