Sorry Dave,
I got a little busy with some work projects, but am looking into it.
Can you please provide me with the following info...
- What version of OS/2 are you using on the machine (and test machines) in question?
- Have you uprgraded or installed fixes for any of the following... TCPIP, REXX, networking in general?
OS/2 (as of WSeB) had a "bug" in the original TCP/IP stack (which was fixed in later releases such as WSeB CP2 and CP2PF) that would cause the stack to lock and no longer route or respond to TCP/IP traffic if the machine received a certain type of attack/packets (I dont remember the specifics of the cause, but this might be your issue).
I run WSeB CP2PF (and have run the earlier releases) and once I switched to CP2 and CP2PF (or applied the TCPIP fixes to WSeB original) never ran into the problem you are describing again. I've run multiple websites from the same box - which handles ooodles of traffic (lots too!

) and not experienced any issues since applying the fix or switching to a later release of WSeB.
I
*had* a reboot tool I used to use (but can't find it - will rewrite it for you) that I used for that and other situations... what I did was assign a machine an IP like this... XX.XX.XX.100, and then an alias on the same card for XX.XX.XX.150 - my second machine was XX.XX.XX.101 with no alias. If the second machine saw no response (via pinging the first) on IP XX.XX.XX.150, it would alias itself to that address and assume the functions of the first machine. The first machine, when rebooted would tell the second machine "I'm up... un-alias that IP" and then check to see when the 2nd machine dropped the alias. It would then alias itself to the .150 address and resume handling traffic.
I should be able to re-write that script so that it checks any other machine or location on the net, and failing a response, initiates a reboot. This can be handled a few different ways... either a simple ping utility that times out properly (some dont seem to, and just hang waiting for a ping response) or using something like wGet or Curl to retrieve a small page from someplace with a timeout - and if that timeout occurs, initiate a reboot.
So that brings up the
next question... do you have a webserver on another machine that has a small page (or that you can create a small page on) that the script can attempt to access? If so, I can have a script written pretty quickly... it would use some custom stuff in REXX and the GetHTTP library (or wGet) from Hobbes.
But that brings up
one final question... what version of REXX are you using? (ObjectREXX or Classic REXX)? ObjectRexx eventually crashes the REXX.DLL after an app is running for a long time using Stem Arrays - there is a better version on Hobbes that doesn't crash as quickly - but you may not need it depending on what version of Warp you are using (WSeB CP2PF and eCS 1.X DO show this problem - but unless you are using lots of REXX scripts that create a lot of Stem Arrays, you should have that problem... and if you are running CRexx and not ORexx, you wont run into the problem at all).
-Robert