NoMachine server on Arch no longer connects, Error is 22, ‘Invalid argument’.

Forum / NoMachine for Linux / NoMachine server on Arch no longer connects, Error is 22, ‘Invalid argument’.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #44064
    pomodoro
    Participant

    I’ve installed NoMachine Server on a PC running Arch Linux and have been connecting to this PC from another one running Windows 10 on the same LAN for two months without issue, yesterday suddenly the connection was dropped, since then I can no longer connect successfully, when I connect the remote desktop appears for 2 o 3 seconds and the connection closes.

    Tried lots of things, reinstalling both client and server, restarting both machines several times but nothing solves the issue.

    The following error is printed on the client session log (It’s the same error every time):

    41464 28732 2023-04-28 18:42:27 489.809 Io/Io: ERROR! Descriptor FD#16732 out of range in method ‘pipe’ context [A].
    Error: Descriptor FD#16732 out of range in method ‘pipe’ context [A].
    41464 28732 2023-04-28 18:42:27 489.809 System/System: Abort called for system at 0x000000006a995f40.
    41464 28732 2023-04-28 18:42:27 489.809 System/System: Error is 22, ‘Invalid argument’.
    41464 28732 2023-04-28 18:42:27 489.809 System/System: ERROR! Killing the current program.
    Error: Killing the current program.

     

    I’ve also attached logs collected from sever.

    #44095
    Britgirl
    Participant

    It could be a client-side issue. We would need full Player logs from Windows machine you are connecting from, so we can check. You can post them here or submit to forum[at]nomachine[dot]com.

    #44099
    pomodoro
    Participant

    It was indeed a client-side issue, I don’t know what triggered it, but after installing a new version of my video card drivers on the client machine, the crash solved by itself.

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

You must be logged in to reply to this topic.