- This topic has 2 replies, 2 voices, and was last updated 10 years, 4 months ago by
.
-
Posts
-
I am using the latest version of NoMachine for OS X, installed earlier this month. I can’t see any obvious way to tell what version I am running. Both client and server are Macs running OS X 10.9.4. The server is running on a 2013 headless Mac Mini (no monitor, keyboard, or mouse) and the client on a 2014 RMBP. Functionally, the App seems to work very well, but I have an issue that is causing me a problem. On the Server, NoMachine is posting a tsunami of identical messages to the Console Log. There are about 25 such messages per second. Each message reads “nxnode.bin: CGSServiceForDisplayNumber: Invalid Display 0x41dc9d03”. The primary problem is that I use the Console Log as a place where my App writes important diagnostic information. But NoMachine fills the Log within less than 3 minutes, after which older messages are scrolled off and lost. When the Console runs it consequently reports >100% CPU usage, which causes me problems elsewhere.
Any ideas?
Also, how many instances of nxnode.bin and nxserver.bin should be running on the client? I show 2 and 4 respectively.
We are still investigating issue with ‘CGSServiceForDisplayNumber: Invalid Display 0x41dc9d03’ flood.
4 nxserver.bin and 2 nxnode.bin instances is OK when someone is connected to that machine.
To check you software version please open NoMachine Player application, go to ‘Preferences’ then to ‘Updates’.
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.
This topic was marked as closed, you can't post.