Service stops running – how to troubleshoot?

[bsammon]

So, every now and then, one of our computers (so far it’s the same one each time) has the NoMachine service stop, and the service needs to be restarted.  And, as dictated by Murphy’s law, this is usually discovered when there are relatively few people in the office.

Any advice–or any documents I should read–about how to start troubleshooting this?

I’ve learned that there’s logfiles in %PROGRAMDATA%/NoMachine/var/log , and I’ve looked at them a little, but I’m not sure what to look for, which logfile is the most useful, or what verbosity log-level I should be using, or even, whether these logfiles are just the wrong place to be starting in.

This is a computer running Windows 11 Home/Business.

 

[Britgirl]

Can you send them to us and we’ll take a look? 🙂 Send them to forum[at]nomachine[dot]com. Zip up the entire var folder from the Windows 11 machine, we can start from that.

Then we’ll give you some further instructions.

[bowlsys]

Having a similar problem, service starts then stops.

What is shown in application event log is:-

Application Error 1000 Faulting application name: nxserver.bin, version: 8.16.1.0, time stamp: 0x00000000 Faulting module name: OLEAUT32.dll, version: 10.0.26100.3624, time stamp: 0xf9de6395 Exception code: 0xc0000005 Fault offset: 0x000000000009eaf3 Faulting process id: 0x4B44 Faulting application start time: 0x1DBA0AC0E6634FF Faulting application path: C:\Program Files\NoMachine\bin\nxserver.bin Faulting module path: C:\WINDOWS\System32\OLEAUT32.dll Report Id: bdf7c7ac-a710-42b2-950d-cc1db345f434

This happens before I am able to connect to this server.

Running NoMachine free version on Windows 11 24H2. NoMachine version 8.16.1

[bsammon]

Email sent.

My sense of the exact timetable of events is a little fuzzy, unfortunately.

If/when this problem recurs, I hope to gather more detailed and precise information.

 

[bsammon]

The problem has reoccurred.

As I write this message, the computer is inaccessable via NoMachine.  It is on the network, and HTTP and SMB and ICMP traffic seems to be working fine.

I have made a snapshot of the logfiles while the computer is inaccessible.  The logging level is currently at “7 – Verbose” (and has been for a few days), so the log file is rather large, but the entire log directory tree zips up to a manageable 4MB.

The error message I receive from the client app is “A connection timeout has occurred while trying to connect to <machine> on port <port>” followed by some boilerplate troubleshooting advice.

 

[Britgirl]

bsammon, we have received your logs.

[Author]

Posts