Trying to sort out Enterprise setup

[Kurt]

I ran this command:

cat /var/log/system.log | grep -e nxnode -e nxau >> nxsystem.log

Which said:

nxnode.bin[8648]: BUG in libdispatch client: mach_recv, monitored resource vanished before the source cancel handler was invoked { 0x10b916980[source], ident: 134147 / 0x20c03, handler: 0x7fff6797db47 }

I did not run that kextstat | grep nx command earlier, but running it now doesn’t show anything.

[Britgirl]

But did you actually run the commands I mentioned in my reply here? https://forums.nomachine.com/topic/trying-to-sort-out-enterprise-setup#post-26946

1. Run commands changing nxaudio permissions (if you didn’t do it earlier).

sudo chmod -R 755 /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext
sudo chown  -R root:wheel /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext

2. Run command

sudo kextutil -v 4 /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext

and paste/attach the output to the reply

3. After that check if kext nxaudio is loaded (via kextutil in 2.) using command:

kextstat | grep nxau

[Kurt]

Kext library architecture set to x86_64.

Defaulting to kernel file ‘/System/Library/Kernels/kernel’

Kext library recording diagnostics for: validation authentication dependencies warnings.

Reading loaded kext info from kernel.

Kext rejected due to system policy: <OSKext 0x7ff277512650 [0x7fffa78808e0]> { URL = “file:///Library/StagedExtensions/Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext/”, ID = “com.nomachine.driver.nxau” }

Kext rejected due to system policy: <OSKext 0x7ff277512650 [0x7fffa78808e0]> { URL = “file:///Library/StagedExtensions/Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext/”, ID = “com.nomachine.driver.nxau” }

Diagnostics for /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/nxaudio.kext:

 

The above is the output after running the commands you mentioned.  My reply under your 26946 post mentions needing to whitelist your company Team Identifier.  Can you provide that?  It is a public identifier, so would help with whitelisting for our MDM and maybe would address the issue?  As a side note, in that link you posted, nothing comes up in the Security & Privacy extension under General when I look to ‘Allow’ anything either.

 

Also, another issue just popped up where it says that there are No Available Sessions on this Server after restarting the iMac in the lab twice and also trying: /etc/NX/nxserver –restart

Still get the error.  Not sure what to do about that now as I can’t continue my testing with that client until it is working again.

 

Again, I appreciate all the help you have given so far to help me get this working for us!

[Kurt]

I have an update.  I was able to find your Team Identifier using the code sign command.  For anyone else trying to do this, here is the identifier to authorize via MDM:

493C5JZAGR

Unfortunately, after enabling the kext and restarting my test computers I am no longer able to connect to either of them with that No available sessions on this server error.  I also restarted the Cloud Server service and also rebooted the server itself.

So I am unable to see if that fixed the audio issue.

[Kurt]

Audio is working(!!) on a third lab iMac that I set up since I can no longer connect to the other two.  Now I just need help sorting out that No available sessions on this server error.

[Mth]

Hello.

About that “nxnode.bin[8648]: BUG in libdispatch client”, do you have a crash.report?
If yes, could you provide it with server logs?

The article on how to collect logs:

https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)

Please send the logs to forum[at]nomachine[dot]com using the title of that forum’s thread as the mail’s subject.

/Mth

[Kurt]

Not sure they match exactly what you are looking for, but they are the only two crash reports I could find that deal with nxnode.bin

I still need help with my No available sessions on this server error.  Any suggestions?

 

Thanks.

[Britgirl]

Hi Kurt, what we need is the full set of logs, not just the crash report 🙂

Follow those instructions that Mth provided and then send the whole file to forum[at]nomachine[dot]com.

[Kurt]

Thanks.  If you can help me clarify, where do you need the logs from because the terminology is always confusing.  When Mth says ‘server’, is that the cloud server/linux box, is that the enterprise desktop client/lab iMac, which still gets called server even though it is not a ‘server’, or my desktop client/home iMac, I am trying to connect from?   I’m assuming it is the Enterprise Desktop client I am trying to connect to where you need these logs to be collected?

With that said, making the changes to these files:

1.3. Server on Mac

Step 1 – Set debug level in server.cfg
Edit /Applications/NoMachine.app/Contents/Frameworks/etc/server.cfg, uncomment and set the following:
SessionLogLevel 7

Step 2 – Set debug level in node.cfg
Edit /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg, uncomment and set the following:
SessionLogLevel 7
and:

SessionLogClean 0

Fixes the connection issue temporarily.  I am able to log in successfully.  But, if I choose log out and close out NoMachine, all seems ok.  But if I choose the option to restart the computer, I get the No available sessions on this server error again.

In addition to that error, I also got another error I had not seen before which said:

The session negotiation failed.

Error: Cannot connect to the remote server as user ‘myActiveDirectoryaccountnamehere’

This happened on one of the machines, but when I used another AD account I have available for testing, that worked fine.  But I hope my actual one starts working again.

I am going to collect those logs and send them.  As always, I appreciate the help.

[Britgirl]

HI Kurt, we received the logs. Apologies for not specifying that the logs are meant to be from the Enterprise Desktop host. We’ll provide some feedback soon.

[Britgirl]

Kurt, we’ve found what the problem is and our developers are looking into a possible solution. For some reason no confirmation that session is running is received from the agent, why this is I cannot say, this is what our developers are investigating. So, I am unable to give you an immediate workaround here. It is probable that we will need to send you a patched package, also with debug enabled. I or one of the developers will update the topic soon.

[Kurt]

Thanks for the update.

[Kurt]

Just mentioning that I received that email, installed the software, collected the logs and emailed them back yesterday.

[Britgirl]

A patched package was sent last month. Did you get a chance to try it?

[Author]

Posts