Restart after Server Error

[JMarstrell]

Is there a way to restart the server after an error without closing and restarting my c# application? If not, is there any other way to recover from a ZWaveJS.NET server error?

[marcus-j-davies]

Hi @JMarstrell

I do believe I implemented a Destroy() method on the Driver class.

ZWaveJS.NET/Visual Studio Projects/ZWaveJS.NET/ZWaveJS.NET/Driver.cs

Line 438 in ffb4f89

public void Destroy()

Using this will bring it down, and you will need to fire up a new instance of this class to start over.
Its advisable to check any zombie processes after this - but i'm pretty sure they are terminated.

I need to bring this package up to the latest API level, so any input is welcome

[JMarstrell]

The driver does go through the destroy process. Any attempt to destroy it again after fatal error gives an error.

If I try to create another instance of the driver after a fatal error the server doesn’t fully complete its startup. Not sure if the port 50001 is being released or not. I have been trying to find a way to check.

Thinking about it, the server my be running from a previous crash and an attempt to start the driver again works momentarily and then causes the fatal error. Is there a way to check and stop it or reconnect?

[marcus-j-davies]

Could you provide me a stack trace of a fatal error?

A fatal error should only occur during driver start up.

ZWaveJS.NET/PSI/server.js

Line 43 in ffb4f89

process.stderr.write("1\n");

These are handled later here, where a fatal error event is emitted for the frontend app to restart everything (but not before calling Destroy)

ZWaveJS.NET/Visual Studio Projects/ZWaveJS.NET/ZWaveJS.NET/Driver.cs

Line 517 in ffb4f89

Destroy();

The Terminate method (in the Destroy block) actually sends a message to the runtime, to destroy its own self

ZWaveJS.NET/Visual Studio Projects/ZWaveJS.NET/ZWaveJS.NET/Server.cs

Line 17 in ffb4f89

internal static void Terminate()

ZWaveJS.NET/PSI/server.js

Line 47 in ffb4f89

if(Data.toString().trim() === "KILL"){

You could go for broke and kill the image

Process.GetProcessesByName("Server.psi").kill()