Where do I set the path to nxclient working directory?

Forums / NoMachine for Linux / Where do I set the path to nxclient working directory?

Tagged: 

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #13464
    barth
    Participant

    Hi,

    I have installed NoMachine 5.1.44 on a CC7 machine (CentOS 7) and the server keeps crashing:

    2017 01-09 16:49:36 260.062 14355 NXNODE   WARNING! Cannot renew Kerberos ticket. Error is 2, No such file or directory.
    2017-01-09 16:49:36 274.093 14355 NXNODE   ERROR! Cannot create directory: [path to home of a user]/.nx.
    2017-01-09 16:49:36 274.159 14355 NXNODE   ERROR! Error is: 13, ‘Permission denied’.
    2017-01-09 16:49:36 274.207 14355 NXNODE   ERROR! Cannot create nxclient working directory: [path to home of a user]/.nx. Error is: Permission denied
    2017-01-09 16:49:36 274.445 14355 NXNODE   WARNING! PA_SendCommandCli: Unable to open cli socket. Aborting command [set-default-source ] execution.
    2017-01-09 16:49:36 274.965 14077 NXSERVER WARNING! Node localhost:4000 from session C945AA3E6AB51DFCF38BAF4746F1E950 reported: Error: Cannot create nxclient working directory: [path to home of a user]/.nx. Error is: Permission denied
    2017-01-09 16:49:36 301.199 14077 NXSERVER WARNING! Session C945AA3E6AB51DFCF38BAF4746F1E950 crashed on display 0.
    2017-01-09 16:49:36 301.284 14077 NXSERVER WARNING! Maximum errors for local session [localhost:4000] reached.

    The problem is that the server tries to create the nxclient working directory in a home directory that is not accessible by root. Where can I configure the path to this directory ?

    Thank you !

    Barth

    #13491
    Cato
    Contributor

    Hello barth,

    Your issue could be solved in two ways:

    1. Allowing access of nxnode process to user’s home directory.

    2. Using alternative location for ‘.nx’ directory.

    First method:

    We need to establish why nxnode is denied access. Are you using AFS, NFS or any other specific file system? You stated that directory is not accessible by root. This shouldn’t matter because nxnode process runs on behalf of connected user. The only exception is when session is started for root himself. In such case nxnode runs impersonating nx user. If you use AFS perhaps you experience this bug:

    https://www.nomachine.com/TR10N07275

    Check if updating NoMachine helps.

    Second method:

    We’ve got feature allowing to configure ‘.nx’ directory location:

    https://www.nomachine.com/FR01E01592&fn=UserNXDirectoryPath

    Note: In article USER_NX_DIRECTORY_PATH key is mentioned, the proper key name is UserNXDirectoryPath.

    #13497
    barth
    Participant

    Thank you very much, the solution 2 worked like a charm !

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

This topic was marked as solved, you can't post.