Cannot create a new display

[Nuertey]

Hello,

For some unknown reason, NoMachine has stopped working for both myself and a co-worker with same error, “Cannot create a new display, please contact your system administrator.” It used to work perfectly fine before, and I am not sure what has changed in the interim.

Connection, session and settings log files are attached in the accompanying zip file.

I am on a Windows Server 2019 Datacenter remote-connecting to a Red Hat Enterprise Linux release 8.7 (Ootpa), Linux 4.18.0-425.3.1.el8.x86_64 with NoMachine version 8.2.3

Any insights are appreciated.

Nuertey

Attachments:

1. NoMachineLogs_08172023.zip

[Nuertey]

Also, attached herein is the NX server.cfg file in case it gives any insight as to what might be the issue. Let me know if any parameter is misconfigured. I am a newbie so may be missing some key configuration parameter.

Note that I do get the below warnings when restarting the server:

[ec2-user@ip-10-102-91-113 ~]$ sudo /usr/NX/bin/nxserver –restart

NX> 162 Disabled service: nxd.

NX> 162 Disabled service: nxserver.

NX> 162 Service: nxnode already disabled.

NX> 111 New connections to NoMachine server are enabled.

NX> 161 Enabled service: nxserver.

NX> 162 WARNING: Cannot find X servers running on this machine.

NX> 162 WARNING: A new virtual display will be created on demand.

NX> 161 Enabled service: nxd.

 

Thanks

Nuertey

[Nuertey]

And here is the node.cfg attached.

Nuertey

[Britgirl]

Both second attachments didn’t attach.

Before you do anything else, and before we investigate, I suggest updating from 8.2 to 8.8 which is the current version. Please do this on both client and server sides. A number of issues have been fixed since 8.2, such as a possible nx daemon crash.

If, after updating, you are still getting the same problem, resubmit server side logs and Player logs from the Windows machine.

[wespiard]

I am actually in the same situation. Running RHEL 8.8 and NoMachine 8.8.1-1.

I started getting this error recently as well. My guess is from some package(s) that updated in RHEL, as my issues started happening after I ran a dnf update.

[Nuertey]

Hi @Britgirl,
The machines were updated but the problem still persists. The logs are attached as directed.

And @wespiard, our issues must be the same then since I recall that I also had to do “sudo dnf update” to ensure that my repos were up to date before installing the Red Hat Development Toolset.

Perhaps you should attach your log files as well so the support team has more datapoints with which to use to troubleshoot. I followed the instructions on this link for how to collect the logs: https://kb.nomachine.com/DT07S00244

Nuertey

Attachments:

1. NoMachine-log.tar.gz
2. user_nxdir.tar.gz
3. NoMachineClientLogs_ec2-user-2023-08-22.zip

[wespiard]

I collected them the other day — I’ll attach them now.

Again, I’m running RHEL 8.8 and NoMachine 8.8.1-1. If it matters, nx-libs and nxagent are version 3.5.99.26-1.

Attachments:

1. user_nxserver.tar.gz
2. NoMachine-server-log-2023.08.21-11.41.41.zip
3. NoMachine-client-log-2023.08.21-07.44.10.zip

[Britgirl]

I’m running RHEL 8.8 and NoMachine 8.8.1-1. If it matters, nx-libs and nxagent are version 3.5.99.26-1.

That “3.5.99.26-1.” indicates an NX-derivative which is not from NoMachine and it could be interfering with the NoMachine software. So, uninstall the derivative and verify if the issue continues.

If it does, please check or share .xsession-errors file in user’s homedir on server, and the /var/log/messages or journalctl logs.

[wespiard]

I have [removed]server installed as well, that’s probably where the nx-libs and nxagent packages are from. I uninstalled it now for testing and am getting the same error with NoMachine.

There is no .xsession-errors file or similar in my user folder.

The following is all that I see in /var/log/messages after attempting to connect with NoMachine:

Aug 23 15:55:33 systemd[1]: Started Session 139 of user wespiard.
Aug 23 15:55:33 systemd[1]: session-139.scope: Succeeded.
Aug 23 15:55:34 systemd-logind[1241]: New session 140 of user wespiard.
Aug 23 15:55:34 systemd[1]: Started Session 140 of user wespiard.
Aug 23 15:55:35 systemd-logind[1241]: Session 140 logged out. Waiting for processes to exit.
Aug 23 15:55:38 systemd[1]: session-140.scope: Succeeded.
Aug 23 15:55:38 systemd-logind[1241]: Removed session 140.

[Nuertey]

Here are my journalctl logs, excerpted and fully attached:

sudo journalctl -x |grep -i error

Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1653]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1653]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1653]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1653]: Fatal server error:
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1653]: (EE) Server terminated with error (1). Closing log file.
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1687]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1687]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1687]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1687]: Fatal server error:
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1687]: (EE) Server terminated with error (1). Closing log file.
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1696]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1696]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1696]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1696]: Fatal server error:
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1696]: (EE) Server terminated with error (1). Closing log file.
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1705]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1705]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1705]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1705]: Fatal server error:
Aug 23 11:00:47 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1705]: (EE) Server terminated with error (1). Closing log file.
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1714]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1714]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1714]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1714]: Fatal server error:
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1714]: (EE) Server terminated with error (1). Closing log file.
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1723]:         (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1723]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1723]: (EE) NVIDIA:     system’s kernel log for additional error messages and
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1723]: Fatal server error:
Aug 23 11:00:48 ip-10-102-91-113.xxx.com /usr/libexec/gdm-x-session[1723]: (EE) Server terminated with error (1). Closing log file.
Aug 23 11:00:48 ip-10-102-91-113.xxx.com gdm[1128]: Gdm: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors

Attachments:

1. journalctl-log.tar.gz

[wespiard]

@Britgirl, any updates or ideas?

[katpan]

Hello,

From journalctl:

Aug 23 13:00:48 ip-10-102-91-113.blueorigin.com /usr/libexec/gdm-x-session[1723]: (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the

Aug 23 13:00:48 ip-10-102-91-113.blueorigin.com /usr/libexec/gdm-x-session[1723]: (EE) NVIDIA:     system's kernel log for additional error messages and

Aug 23 13:00:48 ip-10-102-91-113.blueorigin.com /usr/libexec/gdm-x-session[1723]: (EE) NVIDIA:     consult the NVIDIA README for details.

Aug 23 13:00:48 ip-10-102-91-113.blueorigin.com /usr/libexec/gdm-x-session[1723]: (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the

Aug 23 13:00:48 ip-10-102-91-113.blueorigin.com /usr/libexec/gdm-x-session[1723]: (EE) NVIDIA:     system's kernel log for additional error messages and

Aug 23 13:00:48 ip-10-102-91-113.blueorigin.com /usr/libexec/gdm-x-session[1723]: (EE) NVIDIA:     consult the NVIDIA README for details.

Aug 23 13:00:48 ip-10-102-91-113.blueorigin.com /usr/libexec/gdm-x-session[1723]: (EE) No devices detected.

We are still investigating, but it looks like you have to compile or reinstall NVIDIA drivers as we see the advice <Consult the NVIDIA README for details>.`

[Nuertey]

@wespiard, issue these commands, and post the results of the relevant ones here. It will assist the debugging. So far we are honing on NVIDIA drivers for me:

# Post the output of these logs:

sudo journalctl -x |grep -i gdm

cat /var/log/Xorg.0.log

 

# Ensure that inxi is installed. I will use my system/package as an example:

sudo dnf update

sudo dnf whatprovides inxi

sudo dnf install inxi-3.3.29-1.el8.noarch

 

# Post the output of these too:

inxi -aG

inxi –admin –verbosity=7 –filter –no-host –width

 

@katpan and co. are also still investigating.

Regards

Nuertey

[wespiard]

I don’t have an Nvidia GPU installed, just the basic Matrox integrated graphics.

I have no output for sudo journalctl -x |grep -i gdm.

There exists no /var/log/Xorg.0.log, but I do have $HOME/.local/share/xorg/Xorg.1.log, which has some warnings/errors. I have attached it below.

 

The warnings/errors are here for a quick reference:

[1057801.835] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so

[1057801.835] (II) Module vesa: vendor="X.Org Foundation"

[1057801.835]   compiled for 1.20.2, module version = 2.4.0

[1057801.835]   Module class: X.Org Video Driver

[1057801.835]   ABI class: X.Org Video Driver, version 24.0

[1057801.835] (II) modesetting: Driver for Modesetting Kernel Drivers: kms

[1057801.835] (II) FBDEV: driver for framebuffer: fbdev

[1057801.835] (II) VESA: driver for VESA chipsets: vesa

<strong>[1057801.835] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)</strong>

[1057801.835] (II) modeset(0): using drv /dev/dri/card0

<strong>[1057801.835] (WW) Falling back to old probe method for fbdev</strong>

[1057801.835] (II) Loading sub module "fbdevhw"

[1057801.835] (II) LoadModule: "fbdevhw"

[1057801.835] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so

[1057801.835] (II) Module fbdevhw: vendor="X.Org Foundation"

[1057801.835]   compiled for 1.20.11, module version = 0.0.2

[1057801.835]   ABI class: X.Org Video Driver, version 24.1

<strong>[1057801.835] (EE) open /dev/fb0: Permission denied</strong>

[1057801.835] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support`

 

inxi -aG yields the following:
Graphics:

Device-1: Matrox Systems G200eR2 vendor: Dell driver: mgag200 v: kernel ports: active: VGA-1

empty: none bus-ID: 0b:00.0 chip-ID: 102b:0534 class-ID: 0300

Display: server: X.org v: 1.20.11 with: Xwayland v: 21.1.3 driver: gpu: mgag200 tty: 166×32

Monitor-1: VGA-1 size-res: N/A in console modes: max: 1024×768 min: 640×480

API: OpenGL Message: GL data unavailable in console for root.

Output of inxi --admin --verbosity=7 --filter --no-host --width is also attached.

Attachments:

1. inxi_output.txt

[wespiard]

Apparently I couldn’t upload the .log file, so I renamed it as .txt and am attaching it here for Xorg.1.log.

Also, I have an update for my issue.

I am able to get a desktop connected with NoMachine if I use a barebones local user account. If I use my Active Directory login with sssd, it doesn’t work. So it could be something related to my AD user configuration, or something with sssd specifically.

Attachments:

1. Xorg.txt

[Author]

Posts