CRASHING SERVER

[Legacy_WhiteTiger]

               

Hello everyone,

 

I am hosting my module in a dedicated server using nwnx and my server crashed. I expected the nwnx could restart the game, but appears but appeared a window informing that the program has crash I had to click "close" to close the window. The nwnx only restart when I click close window. I would like not need to click close window to nwnx start restart my server and I not need access the dedicated server ever when crash and makeit restart automatically.

 

anyone knows how fix this issue?

               
               

               
            

[Baaleos]

               

Is it a window asking you if you want to debug etc?

 

There are several types of prompt that can occur when the game crashes.

The Windows Error Reporting and the Visual Studio - do you wish to debug etc

 

I think these can all be disabled / changed via registry edits.

 

http://www.howtogeek...-and-windows-7/

http://msdn.microsof...y2a(VS.80).aspx

http://stackoverflow...plication-crash

               
               

               
            

[Legacy_WhiteTiger]

               

Is it a window asking you if you want to debug etc?

 

There are several types of prompt that can occur when the game crashes.

The Windows Error Reporting and the Visual Studio - do you wish to debug etc

 

I think these can all be disabled / changed via registry edits.

 

http://www.howtogeek...-and-windows-7/

http://msdn.microsof...y2a(VS.80).aspx

http://stackoverflow...plication-crash

 

Yes, is exacly that window. If I don't click to close program, the nwnx does not restart the server.

               
               

               
            

[Baaleos]

               

If the registry edits don't work - the only alternative is to make / find a program that can click the popups to dismiss them.

I had to do something similar for garrysmod - a first person sandbox game/server.

 

When certain crashes happened, the restart couldnt happen until the process was completely terminated.

 

What you could do - potentially is Continuously check for Connectivity to your game servers port - when that connectivity fails - to a taskkill / process kill on nwserver.exe

 

A process kill / taskkill will kill the process and any associated prompts.

               
               

               
            

[Legacy_Shadooow]

               

Since this is new issue I would start with "what caused it". Did you make recently any NWNX changes? Installed a new plugin maybe?

 

Also check all the logs and look where they ends that could be helpful, for example if the last thing in nwnserverlog is "playerX died" it might direct you into OnPlayerDeath even where you might have some NWNX calls.

               
               

               
            

[Legacy_WhiteTiger]

               

Since this is new issue I would start with "what caused it". Did you make recently any NWNX changes? Installed a new plugin maybe?

 

No new plugins right now. My nwnx rarely crashes. I've modified the Windows registry settings, I am waiting to check if it worked.

 

Also check all the logs and look where they ends that could be helpful, for example if the last thing in nwnserverlog is "playerX died" it might direct you into OnPlayerDeath even where you might have some NWNX calls.

 

I did not check the logs0 I was concerned about restarting server. =/ Next time I'll check maybe I find something.

               
               

               
            

[Legacy_WhiteTiger]

               

If the registry edits don't work - the only alternative is to make / find a program that can click the popups to dismiss them.

I had to do something similar for garrysmod - a first person sandbox game/server.


When certain crashes happened, the restart couldnt happen until the process was completely terminated.


What you could do - potentially is Continuously check for Connectivity to your game servers port - when that connectivity fails - to a taskkill / process kill on nwserver.exe


A process kill / taskkill will kill the process and any associated prompts.

Unfortunatelly the registry edits did not work. I guess I'll need a task-killer.
               
               

               
            

[Baaleos]

               Have you tried this?

http://blog.laptopma...porting-windows


I managed to get mine disabled part of the way - but not entirely sure what I did to do that.

Now when my server crashes - Dr Watson in the background takes a crash dump which unfortunately takes 1 minute or so-

Once that's done - then Nwnx can restart it
               
               

               
            

[Baaleos]

               Have a look at this : terra I think has a nwnx solution : not sure if it works or not I tried a .net approach to do the same thing


https://onedrive.liv...FB0C3A645B!1141