Error is 5: Input/output error

Forum / NoMachine for Mac / Error is 5: Input/output error

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #42902
    Mattmil3
    Participant

    Hello,

    One of my colleagues is unable to remote into his iMac from his Macbook Pro, citing this error message.

    Attempts to look online seem to only find closed off results, so I’ve followed their suggestions and attached the three notepad docs / logs from the error session, and compressed as a .zip file.

    NoMachine is latest version on all devices tested from (logs are from my attempt to connect on my Macbook Pro- same model).

     

    All the best,

    Matt

    Attachments:
    #42910
    Britgirl
    Participant

    Hi,

    please tell us:

    1) macOS version of the iMac
    2) macOS version on the Macbook Pro

    We need the server-side logs (so the iMac) which show the input/output error. From a terminal on the iMac, run nxserver --debug --enable all, reproduce the problem and then sudo /etc/NX/nxserver --debug --collect and send us the file to forum[at]nomachine[dot]com. Please use the topic’s title as the subject of your email. Thanks.

    #42912
    Mattmil3
    Participant

    Hello,

    So we set up a Tech Team account as well as the general purpose account, with the Tech Team account having Admin privileges. When punching in that command on the general account it reads ‘not on sudoers list, this will be reported’
    When punching in on Tech Team, it reads: ‘action not found’

    Both systems are OS Monterey.

    Thank you,

    Matt

    #42930
    Britgirl
    Participant

    The user who collects NoMachine logs has to be in the sudoers list.

    https://apple.stackexchange.com/questions/190883/how-to-solve-user-is-not-in-sudoers-file-incident-reported

    If you can’t add yourself to the sudoers list, we can take a look at /Users/nomachine/.nx from the user’s home directory (server side). There won’t be debug since you’ve not enabled, but there might be some clues.

    #42932
    Mattmil3
    Participant

    Hello,

    I’ve been struggling to add the standard user account to the sudoers list. However, I have managed to run the command from the admin account, and yielded a .zip file for you guys to take a look at.

    I will continue attempting to add the standard user to the list.

    Thank you,

    Matt

    #42936
    Britgirl
    Participant

    Thanks for the logs, unfortunately we will need debug enabled.

    Please follow the instructions here: https://kb.nomachine.com/DT07S00243, section “Short instructions” for the server side. From the macOS the user is connecting from, we need the logs as well. Please follow the instructions here: https://kb.nomachine.com/DT07S00244?s=logs#2.2

    Send everything to forum[at]nomachine[dot]com.

     

    #42944
    Mattmil3
    Participant

    Hello,

    I have followed the latest steps sent over via this page: https://kb.nomachine.com/DT07S00243

    I have tried across all three accounts set up on the IMac (two of which have admin privilege) to initiate the $sudo /etc/NX/nxserver --debug --enableall command, including with and without the ‘all’ at the end, to no avail. All it says it ‘Only a user with administrative privileges can use the option: debug’.

    Please can you advise on how to proceed?

    All the best,

    Matt

    #42951
    Britgirl
    Participant

    $sudo /etc/NX/nxserver --debug --enableall

    Remove the $ symbol since this is not needed in the command you need to use.

    sudo /etc/NX/nxserver --debug --enable all

    Then on the mac you are connecting from, open the NoMachine UI, Player -> Security panel -> Don’t delete log files on exit checkbox must be selected.

    Reproduce the problem. Then collect the logs:

    sudo /etc/NX/nxserver nxserver --debug --collect on the server. From the client side, zip up the entire userhome/.nx folder.

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.