** NEW ** This small utility constantly monitors your NWN server program(s) and reloads your modules using zero to one percent of your CPU. Nwmonitor.exe polls the windows processes looking for your server. Should the program fail to locate your server, the server program is restarted with all of the parameters you pass. This program was designed to be a replacement for the cmd prompt software, nwman and will work in conjunction with FireDaemon or stand-alone. Requires .NET runtime support.
Okay, all changes are now in place and stability is -vastly- improved. Program now checks for two additional entries in your INI files (as outlined in the README.TXT file - installed in your "SAVELOG" directory), one entry determines the time to "pause" while waiting for the server to load (default now ramped up to 30 seconds), the other is a timeout period where the monitor presumes the server has "hung" at 100% cpu cycle. The 3.08 revision would occasionally check the process at the same time as a 100% cpu peak and think the server was hung. Thanks for all the positive feedback guys. One final note, I used a different install builder this time so you will have to uninstall your old program before installing this one. T
Posted by mikdrad at 2004-02-2119:23:00
I have the same problem as listed below... the server loads, and in mid-load of the module, the NWN Process Manager restarts. From what you said below, it's because after 10 sec the manager doesnt detect a running game, and assumes it's locked up... you also mentioned an update, which fixed this problem. I downloaded the most recent version, but the problem exists... have you fixed it? Can I get the update?
Posted by Old_Scores_Transfered at on02/20/04
This is a compilation of the old system into a single score. There were 7 that made this score of 9.72 then rounded to 10.
Posted by giantkin at 2004-02-0507:23:00
Takes mine about 3 min to load bud ;) just as input. heh Giantkin Servers: Realms Of Peril ip: giantkin.servemp3.com:5121 Growing past 300 areas, Bindstones in use! _________________________ GK
Posted by Anonymous at 2004-01-2813:01:00
Chalk me up as another one who would like to see a user set timeout option. Keep up the good work Tomkin.
Posted by Tomkin at 2004-01-2812:03:00
hmm.. I will take a look into that. certainly it won't be hard, I just don't have a lot of time on my hands at the moment. two whole minutes? ouch! minor updates to listing: website url filename (thanks for the catch!)
Posted by Tomkin at 2004-01-2806:39:00
The problem which you are seeing is a result of the upgrade to HotU. Pre-hotu these problems did not exist. This update still looks to make sure the program loaded, but waits up to 30 seconds before polling the process to ensure stability. Various other, very minor, updates also in this version. T
Posted by Anonymous at 2004-01-2709:28:00
This looks like a great program, except that when it attempts to load the server, after about 10 seconds the server shuts down and then nwmonitor starts it again. This continues in an endless loop. It seems nwmontior thinks the server is locked up and then kills and restarts it. Maybe some kind of timing issue. Is there anyway to get around this?
Posted by Tomkin at 2003-11-2610:05:00
3.0.07 - Nov 26, 2003 - Complete program overhaul using Microsofts new .NET system. New compiler provides a more robust feature set, allowing NWMonitor to do things previously unavailabe. - NWMonitor is now capable of full thread examination. This new functionality allows the program to monitor processes on a much deeper level functionally. This allows for greater reliability in closing your servers down when needed, and making sure they come back up again. - Added ability to detect "hung" processes, and processes that use 100% cpu resources. These processes are determined to be "bad" and the program will first attempt to close, then to "kill" the rogue process. - Better logging, especially in "hung" states, and for multiple server executions. Program now attempts to maintain backups of ALL log files, not just files from logs.0. - Multiple server executions should now be more reliable. - Still using only 0% - 1% CPU!
Site
