brotech

Forum Replies Created

Viewing 15 posts - 31 through 45 (of 90 total)
  • Author
    Posts
  • in reply to: Frequently getting booted off #22179
    brotech
    Participant

    Hello jjgalvez,

    please enable debug, restart nxserver, reproduce the problem and send logs to forum[at]nomachine[dot]com using as mail’s subject, the title of that forum’s thread ‘Frequently getting booted off’.

    The whole procedure of how to collect logs is described in the article:
    https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)

    regards

    in reply to: Forgot to disconnect session and cannot log in again #22151
    brotech
    Participant

    Hello,
    speaking with the administrator of that remote computer probably will be the fastest way to solve login problem.

    Generally, an unexpected close/terminate/kill of nxplayer will immediately close the NX session on the server side. So this should be not the reason for any problem.

    Anyway, first please send the nxplayer logs, so we can verify if the problem is with authorization, or later with reconnect. You can find those logs in your home/.nx directory, the most recent directory starting from R- should contain ‘connection’ which includes valuable information. Send it please to forum[at]nomachine[dot]com making sure to reference the title of the topic in the subject of the mail.

    Regards

    in reply to: Cannot write to .Xauthority #22117
    brotech
    Participant

    Hello,
    please enable debug, reproduce issue, then gather logs as described in article: https://www.nomachine.com/DT10O00163 and send to forum[at]nomachine[dot]com

    Please ensure that mail’s subject is ‘Cannot write to .Xauthority’ so we can track properly that
    issue. If you could attach also the /etc/pam.d directory, it might be useful.
    To make one file which contains the whole pam.d directory, run in a terminal:
    tar -zcf myownpamd.tar.gz /etc/pam.d

    in reply to: Cannot write to .Xauthority #22049
    brotech
    Participant

    Hello,
    Lets focus on remote node. If you have correct permissions when logging in there using SSH, please create backup of /etc/pam.d/nx and then copy /etc/pam.d/sshd over /etc/pam.d/nx. After that, try to start NX session again on the TSN.

    If your remote node uses pam_mount module, then this article might be helpful: https://www.nomachine.com/AR09N00902

    in reply to: Unable to see app on virtual display #21981
    brotech
    Participant

    Hello vt600,

    we checked the output of strace command, and we don’t see anything suspicious. Environment seems to be set correct (DISPLAY/Xauthority), there is a connection to the X display from app, so everything looks OK.

    As I understand in that mate desktop all other apps are working well, and there is no problem with running any application except this Java one, so please try to speak with the developers of that program, how to debug and why their application doesn’t appear on desktop.

    Regards

    in reply to: Unable to see app on virtual display #21930
    brotech
    Participant

    Hello,

    we received the ss.output file, and clearly see that your app is connected to our Xserver.

    Now lets see if output of strace command could give some additional information that’s useful for understanding why you can’t see the app.

    Please run a command in terminal:

    strace -v -f -o java.trace <program command line>

    and share with us java.trace file.

    in reply to: Unable to see app on virtual display #21924
    brotech
    Participant

    Hello seems, that there is no clear message from your app in provided logs. There could be many reasons why the application doesn’t appear, for example, using fixed DISPLAY variable will provide a similar result.

    Maybe the application reports error messages on its stdout? Could you try to run terminal in your mate desktop, then run your application and save the output if any appears?

    Some information could also give a output of ss command, running when your Java application is running.

    Run another terminal and execute there:

    ss -xp > ss.output

    then share with us ss.output file, and please provide also PID of your Java application.

    in reply to: Not able to connect with NIS account #21825
    brotech
    Participant

    Hello,

    based on your description, it’s unclear if you are connecting, logging in as NIS user and then
    encountering the problem, or if it is a problem with the connection before the authorization stage.

    If you get the problem with connecting to NX Server please attach the nxplayer’s session directory
    locate at a userhome/.nx directory. Its recent directory started with R letter.

    If the problem happens later (during or after authorization), then we would like to see
    nxserver side logs, located at /usr/NX/var/log directory.

    You can send a compressed file directly to forum[at]nomachine[dot]com or attach here.

    in reply to: Cloud Server connection forwarding #21194
    brotech
    Participant

    Hello,
    no there is no ‘transparent’ mode. You can use Guests (thus avoiding log in on Cloud Server) but those connections will be logged as Guests on final host.

    in reply to: Authentication failed, Mac to Ubuntu #20966
    brotech
    Participant

    Hello,
    there is an article which describes this precise configuration:

    How to set up key based authentication with NX protocol
    https://www.nomachine.com/AR02L00785

    Should there be any problems with access to authorized.crt file, they are reported in nxserver.log file instead of nxerror.log.

    In the case of problems, please log on to the desktop of a different user, start terminal, su to root and execute command:

    /bin/bash -c "cd ~ <user> 2>/dev/null && pwd"

    where is the name of user which you are trying to authenticate with key-based authentication.
    Does it return the proper home directory path?

    in reply to: Two nxserver.bin process active and nxnode.bin blocked #20720
    brotech
    Participant

    Hello, if nobody is connected, there should be running one nxserver process (nxserver –daemon) which keeps all nx processes under control, and nxnode agent. When there is no session, the nxnode process is idle. When the system sees it as ‘not active’, it will wake up and start to work when someone connects.

    We were not able to reproduce the behaviour of NX on OS X as in your case, so please share logs with us:

    – Execute the command tar -czf stacks.tar.gz ~/Library/Logs/DiagnosticReports/nx*
    – Execute the command sudo tar -czf nxvarlog.tar.gz /Library/Application\ Support/NoMachine/var/log/

    In the Finder window you’ll find the files stacks.tar.gz and nxvarlog.tar.gz. \
    Please send them to forum[at]nomachine[dot]com.

    in reply to: White screen when connecting after one day #20159
    brotech
    Participant

    You could find more detailed information by using ‘ipcs -mp’: columns ‘cpi’ and ‘lpid’ will provide some clues about the involved processes.

    in reply to: White screen when connecting after one day #20151
    brotech
    Participant

    About the ‘there is problem with shared memory’ I need to explain better. It all depends on how Unix is dealing with MIT-SHM shared memory. We suspect an application is leaking shared memory. The operating system is not dealing with these memory leaks by its own. The available shared memory, in the end, is all taken and other applications, like NX, can’t allocate more. Why now? Well, can be some application upgrade… The solution is simple: find out which application is leaking shared memory and fix it. It’s unlikely that the application leaking shared memory is NX, since NX is in use on millions of machines and we had not similar reports from other users, but can be, of course, that’s why we need to investigate on your machine. We are also discussing the option of checking the shared memory in use, and recovering the segments that are clearly the fruit of some application’s leak. And! We have planned to move away from MIT-SHM, and use some shared memory interface that is more modern, multiple times… But the time is never enough.

    in reply to: White screen when connecting after one day #20149
    brotech
    Participant

    Hello jnko,

    sorry I made a typo, it should be ipcs -m instead of -s.

    For question ‘why there is problem with shared memory’ – we suspect an application is leaking shared memory.

    in reply to: White screen when connecting after one day #20123
    brotech
    Participant

    Hello jnko,

    it seems that the white screen problem is related to shared memory.
    Please share here output of commands:
    ipcs -s

    sysctl -a | grep shm

    top -b -n 1

    run through sudo or as root user.

    regards

Viewing 15 posts - 31 through 45 (of 90 total)