New TFS 4.5 Watchdog

[PanTast]

Here is the new Watchdog

:salute:

2021-07-22 update by Artist: Check TFS Resources (https://www.team-fusion-simulations.de/tfsresources) for latest versions.

[ATAG_Colander]

This one is for the new launcher 64 bits.

[=FI=Murph]

Forgive me for being a bit slow on the uptake. What does this do?

[ATAG_Colander]

Forgive me for being a bit slow on the uptake. What does this do?

If you don't know, you don't need it :)

Is the software we use at ATAG to keep the game server running. We shared it before so we are sharing the new version Blitz compatible.

[DD_FT]

Thanks Very Much!

[Teetwo]

Thanks for getting this out so fast.

S!

[BAT13]

Thx for the Job :thumbsup:

Seems to work fine but i can't see anymore my server in the list. :stunned:
Checked my ports and adress. I changed nothing since the 32 bits version.
The 32 version worked perfectly four our training server. :(
I can't understand why...
Any idea ?

Thx again

JP

[SirAthlon]

Many Thanks.

[TWC_Flug]

In the previous Watchdog thread (https://theairtacticalassaultgroup.com/forum/showthread.php?t=8034&p=241335&viewfull=1#post241335), I mentioned that TWC uses a script to "watch the Watchdog". Basically it ensures that Watchdog starts whenever Windows starts up, and also keeps Watchdog running, restarting it if it ever quits for any reason.

It would also be easy to do a few things like check for .NET error boxes that pop up occasionally, and close them if they do. But, I haven't bothered with that yet.

Instructions:

1. Install AutoHotKey (http://AutoHotKey.com)
2. Copy/paste scrip below to a convenient location; update the location of your ATAG_CloDWatchdog.exe in the script
3. Place this script (or a shortcut to it) in your system startup folder so that it auto-starts when windows starts (instructions for locating your system startup folder here (http://www.thewindowsclub.com/startup-folder-in-windows-8))
4. Run netplwiz to make the account that runs the Launcher/WatchDog/AutoHotKey system auto-login when the computer is turned on (instructions here (https://technet.microsoft.com/en-us/magazine/ee872306.aspx)). (Those instructions work for Vista and Win7-8-10; for WinXP the command to run is "control userpasswords2" and instructions are here (http://www.megaleecher.net/Windows_Auto_Logon#axzz4IxspyLtP).) Some discussion about this approach and alternatives here (http://security.stackexchange.com/questions/10170/how-secure-is-windows-auto-logon).

When the script starts (on Windows startup) it checks to see if CloD WatchDog is running. If not, WatchDog is started.

Then every 1 minute it checks whether WatchDog is running (starting it if not) and also clicks the "Start Watchdog" button to ensure that Watchdog is actually doing its job.

So, when the machine is turned on, the account logs in, AutoHotKey starts this script, and the script launches WatchDog and presses the "Start Watchdog" button.


;;auto-start-atagCLODWatchdog.ahk auto-hotkey script.
;;by Brent Hugh, February 2018
;;
;;This script ensures that CloD WatchDog is started and running
;;and that that the "Start Watchdog" button is pressed
;;
;;It checks every 60 seconds.
;;It will also check whenever you manually press ctrl-alt-shift-J, which is helpful for testing purposes
;;
;;To use it, You'll need to
;; 1. Install AutoHotKey
;; 2. Update the location of your ATAG_CloDWatchdog.exe in the script below
;; 3. Place this script (or a shortcut to it) in your system startup folder so that it
;; auto-starts when windows starts

#NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases.
; #Warn ; Enable warnings to assist with detecting common errors.
SendMode Input ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory.

#Persistent
SetTimer, StartWatchdog, 60000
return

+!^j::
Gosub, StartWatchdog
Return

StartWatchdog:
Gosub, RunWatchdog ; make sure Watchdog.exe is started & window open
sleep, 4000
SetControlDelay -1
ControlClick, Start Watchdog, CloD WatchDog,

Return

;;Make sure Watchdog is running & maximized (ie, window open & displaying, not minimized to tray)
;;Put the path to your copy of CloDWatchdog in the line with the XXXXXXXXXXX
RunWatchdog:
DetectHiddenWindows, On
Process, Exist, 4.5 ATAG_CloDWatchdog 64.exe
If (!WinExist("CloD WatchDog"))
Run, "C:\Users\XXXXXXXXXXX\Documents\1C SoftClub\il-2 sturmovik cliffs of dover\4.5 CloDWatchdog 64.exe"
Else
DetectHiddenWindows, Off
If (!WinExist("CloD WatchDog"))
{
WinShow, CloD WatchDog
WinActivate, CloD WatchDog
}
Return

[TWC_Flug]

After #$&*@#$&* Microsoft forced our Win10 machine to upgrade to Win10 "fall creators update" I'm having trouble getting CloD WatchDog to work.

It starts Steam OK, starts launcher64.exe Ok, but when it goes to send commands to launcher64.exe, nothing happens.

It will just sit there at the command prompt saying "4>" or whatever. And then after a while WatchDog will close the Launcher64 window.

A typical log looks like this:


Sending stop command.
Stopped
**** Steam Start ****
Starting...
Started
Waiting 30 secs. to start launcher
**** Launcher Start ****
Starting
Sending Initial Commands...
Launcher Start
Sending common configuration commands
Sending:
Error Connecting to launcher.
Error Sending common configuration commands.
Closing Connection
*** Launcher Stop ***
Connecting...
Sending stop command...
Waiting for launcher to stop...
Launcher stopped
Failed to start!

If I go in & just manually type the commands to start a mission, it seems to work just fine (though WatchDog never recognizes that a mission has started, so it will close the window in short order to 'try again').

Any thoughts?

It was working just fine until "Creators Update" . . . .

[TWC_Flug]

So, as noted above, I never could get 4.5 Watchdog to work on this machine. It's insane because it is working on our other, very similar server just fine & was working on this server just fine until the blasted "Creator's Update".

So I gave up on Watchdog for this server and instead expanded the Auto-Hotkey script we have been to start Watchdog & keep it running, until it does pretty much everything Watchdog does--but without requiring Watchdog at all.

Also it does a few handy things like zapping some of the most commonly encountered error pop-ups that Steam & CloD create. It's not quite as smooth & easy-to-use as Colander's Watchdog but it might be a helpful option for anyone who has trouble getting Watchdog to run, or would like something more flexible & scriptable.

Originally I posted all the code etc here but I thought it might make more sense to post it on its own separate thread instead of highjacking this TFS 4.5 Watchdog thread. The new thread with code, examples, etc is here. (https://theairtacticalassaultgroup.com/forum/showthread.php?t=28305&p=305213#post305213)

[alexbp]

Thanks, this was very usefull!

[Cassius]

Thanks for all information.
I tryed to lanch 4.5 Watchdog and have that


...
[22:58:10] Loading mission ...
[22:58:11]
[22:58:11] =================================================
[22:58:11] System.Exception: File not found
[22:58:11] в ORusJ8aLdW0lLo13cpVbbtV43dm.UKDlEC8UawSvq4YsWKtl4J mNzDD()
[22:58:11] =================================================
[22:58:11]
[22:58:11] =================================================
[22:58:11] System.Exception: File not found
[22:58:11] в ORusJ8aLdW0lLo13cpVbbtV43dm.UKDlEC8UawSvq4YsWKtl4J mNzDD()
[22:58:11] в y7Wv0oLKq9Wow9J4KwK5CVZGuwq.teGNdPxlPycIzKUPlrEdvS 1obfV(zx6w9NLDDzK7dzCAUicIJ0aH0ZvA )
[22:58:11] =================================================
[22:58:11]
[22:58:11] =================================================
[22:58:11] System.Exception: File not found
[22:58:11] в y7Wv0oLKq9Wow9J4KwK5CVZGuwq.teGNdPxlPycIzKUPlrEdvS 1obfV(zx6w9NLDDzK7dzCAUicIJ0aH0ZvA )
[22:58:11] в y7Wv0oLKq9Wow9J4KwK5CVZGuwq.4XDoc1Sz95f08B7cicGLbo 2IxCd(zx6w9NLDDzK7dzCAUicIJ0aH0ZvA )
[22:58:11] в TDvcK9j62rPRnS3C16AJTcurgjW.LE3ACy0cUrOe12V5JnTEiR cbzcnb(String )
[22:58:11] =================================================
[22:58:11]
[22:58:11] =================================================
[22:58:11] System.Exception: File not found
[22:58:11] в TDvcK9j62rPRnS3C16AJTcurgjW.LE3ACy0cUrOe12V5JnTEiR cbzcnb(String )
[22:58:11] в dUMrl8pYRYuNyffzeHdlB6oGOnN.RopPvRaaBVDrD6qTNJpDjF mXo5Q(Dz4E9LPBAjPotiGbjq6rEjaFkEyA )
[22:58:11] в dUMrl8pYRYuNyffzeHdlB6oGOnN.9VgcPhPLsku3O9xDjuRYGE XJEGb(String )
[22:58:11] в 3Bua6OK7vC2E7cnFtxIbi6v37iQ.u8ob1Sbg3Afq0k0uFStJaW CxN8mA(String )
[22:58:11] в u7mRAv4sLKFSZB6M8LZBq0uzDdR.fSrC77ccFy4w5jBYVEvbhd CsYR9A(String , dCkAe0QLYwNICjESJvD8oJuT0KV )
[22:58:11] =================================================
[22:58:11] 8>[22:59:05] Server: Cassius Calhoun enters the battle.
[23:00:05]
[23:00:05] 8>[23:00:05] battle stop
[23:00:05] 9>[23:00:05] exit
[23:00:05] Server: Cassius Calhoun has had enough of this!
[23:00:05] 10>


Server started OK and I see it on other PC, and can connect to the server. But...
And I notice, that those problem with System.Exception: is with old 32 Commander Repka, early worked perfect with 4.312, not now.
Only I did, install Blitz and Net.Framework 4.71
System Win7\64
Any ideas?
Search for this fact sends to
https://support.microsoft.com/en-us/help/823196/prb-you-receive-a-system-io-filenotfoundexception-error-when-the-clien
:doh:

[Cassius]

In some cases, the lack of any answer, in itself, is already the answer. :)

[♣_Spiritus_♣]

Sorry this is out of my knowledge area. Hopefully someone can help you out.

[Salmo]

Thanks for all information.
I tryed to lanch 4.5 Watchdog and have that


Server started OK and I see it on other PC, and can connect to the server. But...
And I notice, that those problem with System.Exception: is with old 32 Commander Repka, early worked perfect with 4.312, not now.
Only I did, install Blitz and Net.Framework 4.71
System Win7\64
Any ideas?
Search for this fact sends to
https://support.microsoft.com/en-us/help/823196/prb-you-receive-a-system-io-filenotfoundexception-error-when-the-clien
:doh:

The errors occur after/while the mission is loading. They are not server errors but mission script errors. "file not found" looks like the script is trying to load/launch a submission & not finding the file. The offending code is probably in the OnBattleInit() or the OnBattleStart() code routines. Either the sub-mission file does not exist, or perhaps the path to sub-mission file in the script is wrong. I'd be looking for a code line that has "postmissionload" in it & check that the file path is on that line.

[Cassius]

Big thank you.
I'll try to launch simple mission without submission loading.

[\Hawk/]

Thanks for getting this out so fast.

S!

Off topic:
I can't find this on google.
What does the s! symbol mean?

[Cassius]

Off topic:
I can't find this on google.
What does the s! symbol mean?
This means a salute. :salute:

[\Hawk/]

This means a salute. :salute:
Aaah! many many thanks and S!
:salute:

[Cassius]

.

[Cassius]

.

[ATAG_kiwiflieger]

I think that relates to old ATAG mission functionality that became unnecessary after scripting changes, I'm not sure if it can be re-enabled though.

EDIT:

After #$&*@#$&* Microsoft forced our Win10 machine to upgrade to Win10 "fall creators update" I'm having trouble getting CloD WatchDog to work.
Flug, just saw your post on Watchdog. I know this is a few months late, but did you make sure the port specified in the 'Launcher listen port' in the Watchdog settings is the same as the one on the 'IP=' line under [Console] in the confs.ini?

[Cassius]

.

[DD_FT]

You could try and edit ClodWatchdog.ini, and change the values in there.


[General]
MissionTimeOut=245

Now I am not sure whether it will work... I think it will.

Alteernatively, you could add a line to the file settings.cmd:


timeout 14410 sc exit

Where the number entered is the number of seconds that will pass before the command 'exit' is being sent to the server, and it will exit.
(14410 is about 4 hours...)

Good Luck!

[Cassius]

.

[Cassius]

.