Server status : Querying the server problem again

Forum / NoMachine for Windows / Server status : Querying the server problem again

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #32381
    Babok
    Participant

    Version: 7.2.3

    OS: Windows 10

    Since the latest update the bug is back.

    same issue as: https://forums.nomachine.com/topic/server-status-querying-the-server

    #32405
    zaq
    Participant

    Hello Babok,

    Did you do update by installing *exe file with new version or by clicking in Settings in GUI? Which was your previous version?

    #32408
    Babok
    Participant

    Previous version was 7.1.3

    Installed with exe after I downloaded from your website.

    #32458
    zaq
    Participant

    Hi,

    We weren’t able to reproduce the error. Could you check your NoMachine
    Service shortcut? It’s the path:

    C:\ProgramData\Microsoft\Windows\Start
    Menu\Programs\NoMachine\NoMachine Service

    and check target like you can see in the attached picture.

    Also logs will be helpful, please gather them like it is described in:

    https://www.nomachine.com/DT10O00163#1.4

    and send log archive to:

    forum[at]nomachine[dot]com

    #32489
    Babok
    Participant

    Hey,

    I got the same path for services “C:\Program Files (x86)\NoMachine\bin\nxplayer.exe” –dialog status

    And the other one is disabled: NoMachine device server on services “C:\Program Files (x86)\NoMachine\bin\nxservice64.exe” –servicemode”

    Attachments:
    #32491
    Babok
    Participant

    today log

    Nxservices.log

     

    6748 6752 14:09:26 722 nxexecExecServer: Info: Server process running with pid 6824.
    4668 6728 16:01:37 510.858 nxserviceRunEventLoop: ERROR! Read failed.
    4668 6728 16:01:37 510.858 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    13376 11336 16:01:37 532 nxexecExecServer: Info: Server process running with pid 14308.
    4668 6728 16:01:38 534.055 Monitor/FileReadMonitor: WARNING! Canceling busy thread 8808 for FD#7.
    8456 13844 16:01:38 848 nxexecExecServer: Info: Server process running with pid 13912.
    2848 7260 16:01:39 322.696 nxserviceRunEventLoop: ERROR! Read failed.
    2848 7260 16:01:39 322.696 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    10328 6524 16:01:39 339 nxexecExecServer: Info: Server process running with pid 1308.
    2848 7260 16:01:39 555.711 nxserviceRunEventLoop: ERROR! Read failed.
    2848 7260 16:01:39 555.711 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    13716 13968 16:01:39 574 nxexecExecServer: Info: Server process running with pid 13368.
    2848 7260 16:01:40 014.170 nxserviceRunEventLoop: ERROR! Read failed.
    2848 7260 16:01:40 014.170 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    13832 14200 16:01:40 031 nxexecExecServer: Info: Server process running with pid 12156.
    2848 7260 16:01:40 473.818 nxserviceRunEventLoop: ERROR! Read failed.
    2848 7260 16:01:40 473.818 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    3368 13464 16:01:40 490 nxexecExecServer: Info: Server process running with pid 13692.
    10764 13816 16:03:38 181 nxexecExecServer: Info: Server process running with pid 10440.
    14292 13380 16:05:09 403.367 nxserviceRunEventLoop: ERROR! Read failed.
    14292 13380 16:05:09 403.367 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    6228 6024 16:05:09 448 nxexecExecServer: Info: Server process running with pid 11696.
    11964 7492 16:05:10 300 nxexecExecServer: Info: Server process running with pid 13476.
    11520 13340 16:05:10 787.344 nxserviceRunEventLoop: ERROR! Read failed.
    11520 13340 16:05:10 787.344 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    7876 3316 16:05:10 809 nxexecExecServer: Info: Server process running with pid 8980.
    14292 13380 16:05:11 230.345 Monitor/FileReadMonitor: WARNING! Canceling busy thread 1460 for FD#7.
    11520 13340 16:05:11 329.347 nxserviceRunEventLoop: ERROR! Read failed.
    11520 13340 16:05:11 329.347 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    14304 1308 16:05:11 350 nxexecExecServer: Info: Server process running with pid 2504.
    11520 13340 16:05:11 815.359 nxserviceRunEventLoop: ERROR! Read failed.
    11520 13340 16:05:11 815.359 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    13740 11856 16:05:11 832 nxexecExecServer: Info: Server process running with pid 13372.
    11520 13340 16:05:12 272.717 nxserviceRunEventLoop: ERROR! Read failed.
    11520 13340 16:05:12 272.717 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    7864 4704 16:05:12 289 nxexecExecServer: Info: Server process running with pid 5980.
    11520 13340 16:05:12 743.815 nxserviceRunEventLoop: ERROR! Read failed.
    11520 13340 16:05:12 743.815 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    11108 11416 16:05:12 760 nxexecExecServer: Info: Server process running with pid 14308.
    11368 7444 16:07:29 206 nxexecExecServer: Info: Server process running with pid 13740.
    7712 8140 16:08:31 769.753 nxserviceRunEventLoop: ERROR! Read failed.
    7712 8140 16:08:31 769.753 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    13844 2416 16:08:31 790 nxexecExecServer: Info: Server process running with pid 12364.
    14244 13924 16:08:32 536 nxexecExecServer: Info: Server process running with pid 12644.
    3728 2616 16:08:33 016.049 nxserviceRunEventLoop: ERROR! Read failed.
    3728 2616 16:08:33 016.049 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    13756 13864 16:08:33 035 nxexecExecServer: Info: Server process running with pid 8888.
    3728 2616 16:08:33 333.049 nxserviceRunEventLoop: ERROR! Read failed.
    3728 2616 16:08:33 333.049 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    2720 3308 16:08:33 354 nxexecExecServer: Info: Server process running with pid 14308.
    3728 2616 16:08:33 798.053 nxserviceRunEventLoop: ERROR! Read failed.
    3728 2616 16:08:33 798.053 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    9404 5152 16:08:33 814 nxexecExecServer: Info: Server process running with pid 4600.
    3728 2616 16:08:34 250.064 nxserviceRunEventLoop: ERROR! Read failed.
    3728 2616 16:08:34 250.064 nxserviceRunEventLoop: Error is 32, ‘Broken pipe’.
    3368 8780 16:08:34 266 nxexecExecServer: Info: Server process running with pid 13480.
    13920 8792 17:26:49 646 nxexecExecServer: Info: Server process running with pid 2864.
    7656 1040 17:27:19 368.232 Monitor/FileReadMonitor: WARNING! Canceling busy thread 8748 for FD#7.
    6264 6268 17:27:51 458 nxexecExecServer: Info: Server process running with pid 6328.
    4372 6236 18:06:58 553.416 Monitor/FileReadMonitor: WARNING! Canceling busy thread 6336 for FD#7.
    4376 13092 18:37:37 646 nxexecExecServer: Info: Server process running with pid 8388.
    14016 11080 18:39:31 052.323 Monitor/FileReadMonitor: WARNING! Canceling busy thread 2664 for FD#7.
    6272 6276 18:41:52 973 nxexecExecServer: Info: Server process running with pid 6336.
    4424 6248 18:43:18 475.980 Monitor/FileReadMonitor: WARNING! Canceling busy thread 6344 for FD#7.

    #32553
    Babok
    Participant

    The issue is fixed on the latest release: 7.3.2

    Thanks again to listen us.

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

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