brotech

Forum Replies Created

Viewing 14 posts - 76 through 89 (of 89 total)
  • Author
    Posts
  • in reply to: Adding a node to an Enterprise Server #12409
    Avatarbrotech
    Participant

    Hello Pnnord,
    the reason of that behaviour could be the same UUID on remote nodes (appserver34, appserver35) which could happen if one is a clone of another. You can verify it for example looking in /usr/NX/var/log/nxserver.log file which provide an extended description, e.g.,

    2016-09-20 17:38:19 973.162 21624 NXSERVER ERROR! Cannot add node ‘appserver34:4000’: node ‘appserver35:4000’ with the same UUID 174be7e5-388f-40fe-8adc-46220c78ab49 already exists in database.

    In that case, there is a solution here for it in the following forum post:

    https://www.nomachine.com/forums/topic/nomachine-host-not-appearing-in-connections-list-after-installing-cloned-image

    in reply to: Unable to access remote centos 7 server #11675
    Avatarbrotech
    Participant

    Hello,
    it seems that you don’t have a desktop environment installed, or nxnode doesn’t find it.
    In this case, this article could be helpful: ‘How to solve error ‘Cannot find the default environment’ on Linux headless machines’ (https://www.nomachine.com/AR06N00891)

    If you have a correct and existing command set in DefaultDesktopCommand
    key in node.cfg, then please enable logs in server and node, restart the server
    and connect using the client.

    Reproduce problem, collect logs and send them to forums[at]nomachine[dot]com using
    “Unable to access remote centos 7 server” as e-mail’s subject.

    The procedure to collect logs is available here: https://www.nomachine.com/DT07M00098

    Regards

    in reply to: SL 6.5 cannot locate X server #11536
    Avatarbrotech
    Participant

    Hello,
    so far we were not able reproduced problem using Scientific Linux 6 in its default installation with desktop, regardless whether ipv6 is enabled or disabled.

    Could you provide more info about what SL you’ve installed exactly, or if you’ve customize it in any way? For example the output of rpm -qa (all installed packages) could help us replicate the same environment. Are you using any Display Manager or just starting desktop using startx command ?

    Then please consider re-enabling debug, restart nxserver and send to us logs again after display 0 became available. The logs you sent to us before don’t contain debug of daemon server which is searching and reporting local X server.

    Please look for the current working authority file of Xserver using command: ps -ef | grep X
    Among parameters of that process should also be -auth userhome/.serverauth.pid

    Use path to that file in following command, executed from command like:
    xauth -f userhome/.serverauth.pid list

    It should report all cookies set and in use by current Xserver, and it is likely we can see the cause of the problem from that.

    Please attach also output from /sbin/ifconfig command, and content of /etc/hosts.

    in reply to: SL 6.5 cannot locate X server #11430
    Avatarbrotech
    Participant

    You are using NoMachine product which support only NX connection methods (it doesn’t support SSH).

    About access to the .serverauth, NFS prevent to access file as root which seems to be a reason
    of that issue. Please verify ownership of the .serverauth file, and configuration of NFS.

    Likely option no_root_squash in NFS configuration is needed, for allow to local root account
    access a filesystem exported by NFS. Note that this is insecure which is a reason that in default
    configuration NFS has it disabled.

    in reply to: Server restarts every 5 seconds #11305
    Avatarbrotech
    Participant

    Hello Tim,
    we received logs, and seems that problem is related to your network configuration.

    Could you share with us your /etc/hosts file ? Could be through mail again as in case of logs.

    in reply to: Server restarts every 5 seconds #11286
    Avatarbrotech
    Participant

    We were not able to reproduce this problem on CentOS 7.2.1511. Could you enable logs in server and node configuration file, restart nxserver, reproduce the problem and then send to us whole /usr/NX/var/log directory to forum[at]nomachine[dot]com or attach them here (size is restricted).

    Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT04M00076.

    in reply to: Connect to local display #11285
    Avatarbrotech
    Participant

    Please update NoMachine server to the latest version, and if problem persists, could you enable logs in server and node configuration file, reproduce the problem and then send to us whole /usr/NX/var/log directory to forum[at]nomachine[dot]com or attach them here (size is restricted).

    Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT04M00076.

    /b.

    in reply to: SL 6.5 cannot locate X server #11277
    Avatarbrotech
    Participant

    It seems that nxserver found Xorg but the problem is with reaching cookie of it.
    In particular system xauth reports warning and exits with code 1:
    /usr/bin/xauth: /home/users/weigand/.serverauth.9074 not writable, changes will be ignored

    Its very likely a problem with wrong SELinux context to this .serverauth.9074 file.

    To verify current context you can use command:

    ls -Z /home/users/weigand/.serverauth.9074

    To set correct context you can use this command:

    chcon -Rv unconfined_u:object_r:xauth_home_t:s0 /home/users/weigand/.serverauth.9074

    in reply to: SL 6.5 cannot locate X server #11199
    Avatarbrotech
    Participant

    We were not able to reproduce this problem on SL 6.5. Could you enable logs in server and node configuration file, reproduce the problem and then send to us whole /usr/NX/var/log directory to
    forum[at]nomachine[dot]com or attach them here (size is restricted).

    Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT04M00076.

    in reply to: NX> 598 ERROR: Cannot attach to local server #11195
    Avatarbrotech
    Participant

    We were not able to reproduce this problem on Debian 4.0.4-1+kali2. Could you enable logs in server and node configuration file, reproduce the problem and then send to us whole /usr/NX/var/log directory to forum[at]nomachine[dot]com or attach them here (size is restricted).

    Instructions about debug and collecting logs you can find there: https://www.nomachine.com/DT04M00076.

    Avatarbrotech
    Participant

    Hello,

    please take a look at /LibraryLogs/DisagnosticReports directory for nxexec’s crash report, and send to us. If you’re not able to find the crash report, information about location of such report is stored in /var/log/system.log.

    We’ve started an investigation regarding support for Centrify. This could be provoking this weird behaviour in nxexec.

    in reply to: VNC considered as physical desktop #9542
    Avatarbrotech
    Participant

    NX Server searches for every non-NX X server and makes it available to attach to. The result could be limited to the particular DISPLAY by node configuration key:

    # Specify on which physical display the server must connect.
    #
    # DisplayDefault :0

    What you are seeing is normal.  Right now it is not possible to filter out non-NX X servers. We could consider adding a node configuration key to allow nxserver to filter out, in your case, the xvnc servers.

    in reply to: Problem to connect a Fedora PC #9444
    Avatarbrotech
    Participant

    NoMachine doesn’t currently support the Wayland X server (though we are working on adding it) and Fedora 23 uses this X server as default. You can temporarily switch to lightdm which will use Xorg instead.

    Steps to change display manager from gdm to lightdm are as follows:

    Install lightdm:
    [root@test01 ~]# dnf install lightdm

    Disable GDM:
    [root@test01 ~]# systemctl disable gdm

    Enable LightDM:
    [root@test01 ~]# systemctl enable lightdm

    Reboot to make changes effective:
    [root@test01 ~]# reboot

    /b.

    in reply to: Stop node on multinode server #3340
    Avatarbrotech
    Participant

    Hello,

    You can remove local node using nxserver –nodedel localhost:22.

Viewing 14 posts - 76 through 89 (of 89 total)