Forum Replies Created
Per your instructions, I uninstalled NoMachine from both machines, and re-installed it. As you anticipated, this did indeed solve the problems. I assume there is therefore no further need for me to send you the additional logs you requested.
FYI, I believe the macOS 10.12 -> 10.13 update (and even the 10.13 -> 10.13.1 update) was done subsequent to updating NoMachine from the previous version to 6.0.62 but I can’t be 100% sure on that. But given my experience to date with macOS 10.13 to date, it would not surprise me if it turned out that it was the culprit here. Unfortunately, I am obliged to apply every OSX/macOS update as it it released, so I don’t have the ‘sensible’ option available.
Thanks for your help, Kroy.
Here are the missing nxserver logs from the server side.
OK, I have followed the instructions on the KB page, and replicated the whole process. I have attached both server side and client side logs.
FYI, I had a lot of permissions issues in following the instructions, so I hope you won’t find yourselves burdened by permissions issues when it comes to reading them. I’m not an expert in this stuff, so bear with me if I have gotten anything wrong.
I also include a screenshot of the nx server status from the Client Side
Is it unreasonable of me to be upset that after 5 days and 12 hours nobody from the NoMachine support team has taken a look at this and so much as posted an acknowledgement of the issue?
Add me to the list. I got the Black Screen too. I’ll be stuck using Mac’s lousy Screen Sharing until you get this fixed 🙁
Thanks, fra81. I followed your instructions and it appears to have worked. This is surprising since I had in fact rebooted the Mac Mini several times in an attempt to clear the problem but it has persisted. This time I attempted to quit NoMachine before rebooting. Unfortunately it seems there is no obvious way to do that! I ended up going into Activity Monitor and force-quitting every process that began with nx…. Having done this, nxnode.bin refused to go away. At that point I rebooted the Mac Mini and when it came back to life NoMachine was working normally. I have no idea if any of that made any sense to you, but that’s how it was.
Thanks guys. Happy to hear that 🙂
Update: I just installed OS X Yosemite on both my Mac Mini (Server) and RMBP (Client). The replicated Server screen now has a 4:3 aspect ratio whereas previously it used to fill the 16:9 RMBP screen in correct proportion with no stretching. I have no idea what determines this behaviour. I didn’t do anything previously to produce the 16:9 screen, and have done nothing this time to produce the 4:3 screen. I don’t (and didn’t) see any options in either NoMachine or OS X that would affect this.
Now the torrent of messages no longer appear in the Console Log! Is this because I am now running Yosemite, or is it because my screen aspect ratio is now 4:3?
I can now confirm that the version in use when I wrote the OP was 4.2.24 and that I have now upgraded successfully to 4.2.26. However, the problem still remains, as I guess you may have expected.
Good luck resolving the flood. Apart from that I really enjoy using it and I would really like to be able to recommend it to my user base. I currently have 25,000 active users, although I don’t know how many of them use my product as I do, with a headless Mac Mini.
FYI, with my OP, I did check the box “Notify me of follow-up replies via e-mail”, but I wasn’t notified of your reply to me. I’ll see what happens with this one.