Britgirl

[Britgirl]

Can you share this dockerfile with us so we can check it? Send it directly to forum[at]nomachine[dot]com.

Similar topics have been submitted in the past

NXFrameBuffer failed to start in Docker

Problems with NoMachine in docker

Redis error after time

but in some cases users didn’t come back to us.

Edited: we have the following document for Docker users https://kb.nomachine.com/DT07S00242. Did you check this already?

[Britgirl]

The same errors are present showing it’s not possible to write to the home directory. NoMachine detects that it’s headless (no x server running) and, as expected, tries to create its own virtual display. But since permissions are not set correctly, it fails.

Also, can you show us the output of the ls -la command for each of these?

/rhome/

/home/DV9G49

/rhome/DV9G49/.nx

You mentioned creating a virtual machine with Debian, what are you using to do that?

[Britgirl]

we were seeing the frame buffer error even without the permissions error? What would be causing it then, if the permission error is removed?

Then yes we need to see the logs without the permissions error. Send them over and we’ll check.

[Britgirl]

oneVPL will be in the next update, 8.12, which is going to be in the next couple of weeks.

[Britgirl]

The next time it happens:

Press Windows key + R to open up a Run dialog box. Then, type “eventvwr.msc” and press Enter to open up the Event Viewer utility.

Inside the Event Viewer utility, use the left-hand side menu to select Windows Logs. Then, double click on Application to bring up the Application events in the right-hand side pane.

Inside the Application section, look for an event that states “The following application attempted to veto the shutdown” in the General tab (under the list of events). Since you’ve just forced the warning message to appear, it should be one of the very first listings since the default order is by date/time.

You will be able to find the executable that is causing the warning message. Tell us what it is.

[Britgirl]

This is the log extract which shows the problem with permissions.

These are the only errors that are actually showing:

2959 2959 2024-05-23 15:27:03 985.560 NXSERVER Process initialized with arguments '--virtualsession --sessionid 9C179A65C3D88C951906D21B49D48B78'.
2959 2959 2024-05-23 15:27:04 685.161 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.
2959 2959 2024-05-23 15:27:04 685.247 NXSERVER Handling connection error 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'.
2959 2959 2024-05-23 15:27:04 685.409 NXSERVER ERROR! Received error message from node ':', 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'
3002 3002 2024-05-23 15:27:35 601.923 NXSERVER Process initialized with arguments '--virtualsession --sessionid 2014DAC8AE6D73DF2E5952BC9823277F'.
3002 3002 2024-05-23 15:27:36 242.431 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.
3002 3002 2024-05-23 15:27:36 242.490 NXSERVER Handling connection error 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'.
3002 3002 2024-05-23 15:27:36 242.659 NXSERVER ERROR! Received error message from node ':', 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'
3045 3045 2024-05-23 15:28:07 166.900 NXSERVER Process initialized with arguments '--virtualsession --sessionid 7575FB0F58880F0183A9C512A67CDAB7'.
3045 3045 2024-05-23 15:28:07 841.607 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.
3045 3045 2024-05-23 15:28:07 841.690 NXSERVER Handling connection error 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'.
3045 3045 2024-05-23 15:28:07 841.894 NXSERVER ERROR! Received error message from node ':', 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'
3093 3093 2024-05-23 15:28:38 714.884 NXSERVER Process initialized with arguments '--virtualsession --sessionid 42222011AFC14FECB63EB0041331FCD2'.
3093 3093 2024-05-23 15:28:39 406.174 NXSERVER Read 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n' 78 from FD#16.
3093 3093 2024-05-23 15:28:39 406.258 NXSERVER Handling connection error 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'.
3093 3093 2024-05-23 15:28:39 406.409 NXSERVER ERROR! Received error message from node ':', 'NX> 596 Error: Cannot create /rhome/DV9G49/.nx. Error is 'Permission denied'.\n'
3137 3137 2024-05-23 15:28:49 903.362 NXSERVER Process initialized with arguments '--debug --collect'.

From the logs you sent us it shows that the frame buffer cannot start because of the home directory error.

[Britgirl]

We were able to reproduce similar behaviour and have since opened a Trouble Report. The fix for this issue can be tracked using this link: https://www.nomachine.com/TR03V11111

It will be in the next maintenance release.

[Britgirl]

This is the Trouble Report. Please use the link to monitor its status https://kb.nomachine.com/TR05V11159.

[Britgirl]

It could be. You can verify this by checking whether it happens when activating another window, then going back to the NoMachine client window. In that case you can keep the keyboard grab working correctly when the NoMachine client is selected by clicking the Dock icon, by using Command + Tab and by selecting the window in Mission Control.

[Britgirl]

Hi, are you able to send us the full server-side logs so we can check what’s happening? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

Additionally, any journalctl output (sudo journalctl -x |grep -i gdm) and the output of ps -ef.

[Britgirl]

Hi Zak, can you submit a new topic so that we handle this issue separately?

[Britgirl]

I forgot to post the link to the Trouble Report https://kb.nomachine.com/TR05V11159. You can use that to track when a fix has been released.

[Britgirl]

Can we send you a debug version?

[Britgirl]

We checked the logs and confirm that the problem is the same as the one reported here: https://forum.nomachine.com/topic/nomachine-not-using-gpu-for-encoding#post-47274 related to specific nvidia driver versions. We are currently investigating workarounds, but for the time-being you should try downgrading to an earlier driver version (535.129.03 appears to be ok) or continue to use software encoding.

[Britgirl]

We don’t have an official date for the release yet, but we are working hard to make it available by this summer.

[Author]

Posts