Users can’t login in. Error: Not enough X resources

Forums / NoMachine for Linux / Users can’t login in. Error: Not enough X resources

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #30064
    Avatardrobson
    Participant

    Hi,

    We are getting complaints form our users saying that they can’t log in.  The errors they see are

    “The session negotiation failed. Error: Not enough X resources”

    Extracts from the logs are shown below.
    The lock files are owned by the users.

    Any ideas?  Pretty urgent, this one.  The users are screaming to get in!

    Thanks

    Dave

    Oct 26 12:08:11 freia010 nxserver[29008]: User ‘#####’ logged in from ‘10.215.130.129’ using authentication method NX-password.
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1002-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1007-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1011-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1014-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1018-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1021-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1061-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1083-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1092-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1096-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1120-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1124-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1127-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1157-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1166-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1177-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxnode[29805]: WARNING! Cannot remove lock file ‘/tmp/.X1184-lock’: Operation not permitted
    Oct 26 12:08:48 freia010 nxserver[29008]: ERROR! X resources are not enough to start another session.
    Oct 26 12:08:48 freia010 nxserver[29008]: WARNING! Cannot get display from node: localhost:4000.
    Oct 26 12:08:48 freia010 nxserver[29008]: ERROR! Status ‘Failed’ for ‘started’ session with Id: ‘8717D4EFE1A3AF57FAB27EEFE04C9D4C’
    Oct 26 12:08:48 freia010 nxserver[29008]: User ‘#####’ from ‘10.215.130.129’ logged out.

    #30069
    Avatarbrotech
    Participant

    Hello,
    Every session requires a set of free ports which are calculated based on DISPLAY. Increasing the display limit should increase the pool available and can avoid such problems as the on you are describing. Please, edit server.cfg (/usr/NX/etc) and set value for DisplayLimit key.

    No nxserver’s restart is required. New connections will use new value.

    For example:

    #
    # Set the maximum number of displays reserved for NX sessions.
    #
    DisplayLimit 400

    If such value as 400 is not enough, and there are still problems, maybe it’s worth checking what ports are in use and change the display range. Another useful key is DisplayBase.

    #30089
    Avatardrobson
    Participant

    Thanks brotech, I’ll try that

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.