cron job to test server availability

[phoenix]

I am looking for a way to test if a TNetServer is up and running, some kind of echo or ping I could send to the the TnetServer and get a response so I know if the server is up and running and receiving data or not.

Any one have any ideas about the best way to keep an automated system running which keeps tests whether servers are available?

Ideally, I would be able to use some standard shell commands to interface with TnetServer.

[devomage]

sounds like a lobby server?

[phoenix]

yes, do you know an easy way to test if the lobby server is up and ready and available to be used?

also,does anyone know a good way to tell the latency or how long it takes for a packet to arrive?

[Shifty Geezer]

TNet has a lobby system you can use, TNLobbyClient lobby.

[ArenMook]

also,does anyone know a good way to tell the latency or how long it takes for a packet to arrive?

TNManager.ping, or if you are trying to get latency to something you aren't connected to, you need to send a UDP ping packet via TNManager.Ping().

[phoenix]

TNManager : MonoBehaviour and therefore I need unity to test if the server is up?

I am looking for a way, preferably with either pure mono code like the TNetServer runs without unity or standard linux command line tools which can run automated tests against the servers from a shell which does not have unity installed to determine if the servers are up and running and available.

From http://superuser.com/questions/621870/test-if-a-port-on-a-remote-system-is-reachable-without-telnet

I have found  Netcat  seems to work!

nc -v -z -w2 192.168.0.1 5127

found 0 associations
found 1 connections:
     1:   flags=82<CONNECTED,PREFERRED>
   outif en1
   src 192.168.0.2 port 55255
   dst 192.168.0.3 port 5127
   rank info not available
   TCP aux info available

Connection to 192.168.0.1 port 5127 [tcp/*] succeeded!

And when the TNetServer it is not running it outputs

nc: connectx to 192.168.0.1 port 5127 (tcp) failed: Connection refused