ServerWatch: now with FTP access to the qconsole.log LogFile

[Enforcer]

Hello,

some of you had the Problem to get ServerWatch running because there was not able to access there Log file in the way it was needed.

Not ServerWatch also supports to access the Log file with FTP.
You only need an FTP Server running on the Server which is running you’re Moh Server. As far as i know lot of Game server providers let you access the Log File of the Server with FTP.

To configure it you have to change ServerWatch to FTP Access mode and insert you’re FTP Server host, Login, Password and the full path to the Log File (qconsole.log).

To get the New Version you can auto update you can download the new Version from my temp homepage http://enforcer.homeftp.org/projekte/serverwatch
(my main internet connection is down today)
Therefore also the auto update feature will not work until my other internet connection come back (supposed to be back at 17:00 CET)

Enforcer

[Capt_Obvious]

SWEEEEEEEEEEEEEEEET!!!! Thanx Enforcer you too Cobra for the help. Working great!!!

Toke

[Capt_Obvious]

One slight problem I've encountered here, and I do mean slight. When someone attempts to autoteam select does that return an unknow team into server watch? I'm guessing the answer is yes, but not sure. Also is there any way of disabling auto team select altogether?

Toke

[Enforcer]

One slight problem I've encountered here, and I do mean slight. When someone attempts to autoteam select does that return an unknow team into server watch? I'm guessing the answer is yes, but not sure. Also is there any way of disabling auto team select altogether?


hehe yes thats true, but is is no problem for ServerWatch.
You have to possibilities for TK protection.

The first one is for TDM Games.
The teams get sorted by the points there get. And so a player is blamed for tk if he kills an other player with the same score. Here the Autojoin is no problem.

The second one is the normal one. ServerWatch is looking for the team_join messages. The Players get sorted in there teams that way. You have to choose the team messages based tk detection in the Setup.
On that mode of operation the use of the Autojoin button the player get kicked with an warning message. The default one is just telling him to better do NOT use autojoin ;-)
Also if you restart ServerWatch it is a problem for the program to rate what player is in what team if you use the join team message method.
In that case all players which are rated to play in an unknown team but killed someone by still being in that "unknown" team get a warning message x times and than there get kicked. (both options are use definable)

I think the ServerWatch setup Guide might also help

Enforcer

[Green]

:rolleyes: Hi :)

I've problems to get Serverwatcher to work... :(
Some parts in the program work, can't change nick to allready know use and so... but i can't get respawnkilling to work.. And not the killing spree.
Any ideas?

[Enforcer]

:rolleyes: Hi :)
so... but i can't get respawnkilling to work.. And not the killing spree.
Any ideas?
Yes - looks like your don’t have configured your log file access right in ServerWatch.

You can check the setup if you open the Debug Window and look @ the "Log File" Tab.
If you can see the new Log entry’s from your Moh Server than ServerWatch should work.

Enforcer

[Capt_Obvious]

Enforcer, Cobra...... It is with much regret that I must inform you that my clan will NOT be using Serverwatch as it is just too buggy at the moment. I have tried to be reasonable but currently it just causes more problems than it solves. For instance it was working.... kind of as in it wasnt crashing but it wasnt detecting ANYTHING today, not kills not tks, and this had been working previously, nothing had changed server side (verified this) Then people started complaining about the high pingers so I set the ping limit to 500. Guess what?!? IT KICKED EVERYONE OFF THE SERVER!!! only 2 people had over a 200 ping a 90% of them had pings below 75!!!! This is unacceptable and I dont think I need to say how embarrasing :oops: :evil: :oops: this was to watch as server admin!! The ban features are very cumbersome as well, but the only reason I wanted to get this working was for the tk detection and as I said before that doesnt even work right without absolute cooperation from everyone! When it is working right within 20 minutes or less of it running it kept crashing and would not continue to run until the system was rebooted!! Now in the spirit of beta testing I am including the bits from the exception log from the last several tries to keep this program running. I hope that you can work out these problems but for now its just not for us.

Also nothing had been changed in the serverwatch setup after it was "working". It just started crapping out on me, take my word for what you want, as this is only MHO. More logs are available upon request....

=Agent= Tokeupdude
Server Admin
The Secret Agency
66.230.141.182:12203

-SNIP-
2/17/2003 3:30:31 PM - : Closing FTP-Link to many Errors - Please check youre Setup Exception occured at $004F2424 (Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 108) [

Exception Trace:
[004F241F]{MohaaServerWatch.exe} uFtpLink.TFtpSession.Execute (Line 108, "uftpLink.pas" + 51) + $11
[0041939C]{MohaaServerWatch.exe} Classes.ThreadProc + $1C
[00403C68]{MohaaServerWatch.exe} System.ThreadWrapper + $28
[77E8B2D5]{kernel32.dll} lstrcmpiW + $B4

Except frame-dump:
Frame at $0862FF08 (type: efkFinally)
Code at $00403698
Module "System", Procedure "@HandleOnException", Unit "", Line 0
Frame at $0862FF14 (type: efkFinally)
Code at $004F2455
Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 117
Frame at $0862FF20 (type: efkFinally)
Code at $004F2495
Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 119
Frame at $0862FF88 (type: efkFinally)
Code at $004193AC
Module "Classes", Procedure "ThreadProc", Unit "", Line 0
Frame at $0862FFA8 (type: efkUnknown)
Code at $0862FFAC
Module "", Procedure "", Unit "", Line 0
Frame at $0862FFDC (type: efkUnknown)
Code at $0862FFE0
Module "", Procedure "", Unit "", Line 0]

Log started: 2/17/2003 3:30:42 PM OS: Win2000 Version 5.0, Build 2195
2/17/2003 3:30:58 PM - : Closing FTP-Link to many Errors - Please check youre Setup Exception occured at $004F2424 (Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 108) [

Exception Trace:
[004F241F]{MohaaServerWatch.exe} uFtpLink.TFtpSession.Execute (Line 108, "uftpLink.pas" + 51) + $11
[0041939C]{MohaaServerWatch.exe} Classes.ThreadProc + $1C
[00403C68]{MohaaServerWatch.exe} System.ThreadWrapper + $28
[77E8B2D5]{kernel32.dll} lstrcmpiW + $B4

Except frame-dump:
Frame at $0258FF08 (type: efkFinally)
Code at $00403698
Module "System", Procedure "@HandleOnException", Unit "", Line 0
Frame at $0258FF14 (type: efkFinally)
Code at $004F2455
Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 117
Frame at $0258FF20 (type: efkFinally)
Code at $004F2495
Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 119
Frame at $0258FF88 (type: efkFinally)
Code at $004193AC
Module "Classes", Procedure "ThreadProc", Unit "", Line 0
Frame at $0258FFA8 (type: efkUnknown)
Code at $0258FFAC
Module "", Procedure "", Unit "", Line 0
Frame at $0258FFDC (type: efkUnknown)
Code at $0258FFE0
Module "", Procedure "", Unit "", Line 0]

Log started: 2/17/2003 3:34:18 PM OS: Win2000 Version 5.0, Build 2195
2/17/2003 3:34:30 PM - : Closing FTP-Link to many Errors - Please check youre Setup Exception occured at $004F2424 (Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 108) [

Exception Trace:
[004F241F]{MohaaServerWatch.exe} uFtpLink.TFtpSession.Execute (Line 108, "uftpLink.pas" + 51) + $11
[0041939C]{MohaaServerWatch.exe} Classes.ThreadProc + $1C
[00403C68]{MohaaServerWatch.exe} System.ThreadWrapper + $28
[77E8B2D5]{kernel32.dll} lstrcmpiW + $B4

Except frame-dump:
Frame at $0258FF08 (type: efkFinally)
Code at $00403698
Module "System", Procedure "@HandleOnException", Unit "", Line 0
Frame at $0258FF14 (type: efkFinally)
Code at $004F2455
Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 117
Frame at $0258FF20 (type: efkFinally)
Code at $004F2495
Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 119
Frame at $0258FF88 (type: efkFinally)
Code at $004193AC
Module "Classes", Procedure "ThreadProc", Unit "", Line 0
Frame at $0258FFA8 (type: efkUnknown)
Code at $0258FFAC
Module "", Procedure "", Unit "", Line 0
Frame at $0258FFDC (type: efkUnknown)
Code at $0258FFE0
Module "", Procedure "", Unit "", Line 0]

[Enforcer]

Then people started complaining about the high pingers so I set the ping limit to 500. Guess what?!? IT KICKED EVERYONE OFF THE SERVER!!! only 2 people had over a 200 ping a 90% of them had pings below 75!!!! This is unacceptable and I dont think I need to say how embarrasing :oops: :evil: :oops: this was to watch as server admin!!

really this is funny you have to read the manual !!!
If you set it to 500 and maybe 10 measures all people will be kicked with higher ping that 50.
If you want to keep them on 200 you have to set it to 2000 !!!!! That is clearly to read in Cobras Guide !!!!!


The ban features are very cumbersome as well

It is very powerful i think. You can ban whole clans or people with stupid names. You have to read something about regular expressions. That’s all. (For the first times you can use the extra menu – generate regular Expression or just ban them by right click on the user list)
And what is the general problem I don’t get it ?


but the only reason I wanted to get this working was for the tk detection and as I said before that doesnt even work right without absolute cooperation from everyone! When it is working right within 20 minutes or less of it running it kept crashing and would not continue to run until the system was rebooted!! Now in the spirit of beta testing I am including the bits from the exception log from the last several tries to keep this program running. I hope that you can work out these problems but for now its just not for us.
The problem is that you are using the FTP feature and this is writting in some hours and might have some problem. But you dont help me if you just claim thinks like that !

Also nothing had been changed in the ServerWatch setup after it was "working". It just started crapping out on me, take my word for what you want, as this is only MHO. More logs are available upon request....

Enable all debug logs and send them to me and i can tell you what the problem is.


2/17/2003 3:30:31 PM - : Closing FTP-Link to many Errors - Please check youre Setup Exception occured at $004F2424 (Module "uFtpLink", Procedure "TFtpSession.Execute", Unit "uftpLink.pas", Line 108) [

That is no big deal ;-)
That only means ServerWatch had 10 connection/file transfer problems to your FTP Server and therefore it stopping the communication. (that can be timeouts and thinks like that) As i said i just coded the FTP Feature. And maybe you can imagine that it is not that easy. Because you cant find any other Program doing stuff like that. Try to sync a FTP File on an local hard drive.
One reason for your Problem can for example be, that the FTP Server of your provider don’t want you to be online that long. Therefore it is just dropping your connection and ServerWatch has a problem. And if i look in my code that can exactly be a problem. But the only way to fix such problems like that is to send me all the logfiles from ServerWatch you have.

BTW: ServerWatch had a log of bugs. One reason is the size of it. At the moment i have about 135000 Lines of Code with all libraries.
So errors can happen but i know some people who are running ServerWatch for days now with the latest version. The SSH Link and the Direct file access don’t have any Problems but the FTP really can be your big but also the only problem. So send me the logs and i will fix it. Without the Logs i don’t know what all the situations that can appear on real live :D

Enforcer

[Capt_Obvious]

Ok first off yes I do RTFM, and no I did not see anything in it in reguards to what you mentioned before. I admit though there may have been a slight language barrier as I only speak english, however I am willing to let this go, and the log files will be emailed to you shortly.

Toke

[Enforcer]

Ok first off yes I do RTFM
Toke
I dont wanted to express it that hard :D

BTW: in my small spear time i had today i maybe fixed youre problem. But i only can be sure if you mail me the log


Enforcer

[Capt_Obvious]

done and done

[CobraEF]

Have yu goten it to work tokeupdude ?

[CobraEF]

We have started to test a few of the things that are done on The anticheat.
And the start of the test looks good.
fore now the test`s are going in a locked server.
But i will tell you when it gets closer to realese.

[captain_trips]

OK, I have this thing up and running on two seperate servers and all is well so far except for on the third server. We rented a server from a company that uses Linux. I connect using the ftp option. No matter what I do I can't seem to get access to the qconsole.log file. When joining the server and doing a "rcon password path" command this is what I get back:


/home/mohaa/.mohaa/main
/home/mohaa/main
/home/mohaa/main/zzz_dogmeat_multi_map_fix.pk3
/home/mohaa/main/pak6.pk3
/home/mohaa/main/pak5.pk3
/home/mohaa/main/pak4.pk3
/home/mohaa/main/pak3.pk3
/home/mohaa/main/pak2.pk3
/home/mohaa/main/pak1.pk3
/home/mohaa/main/pak0.pk3
handle1: qconsole.log

What is that handle1: qconsole.log and where the heck is it on the server? It looks like the file is being created but I have no access to it.

That is the problem with our main server that I am trying to fix the second problem that I have is with the auto-join function and tk monitoring. It works but if anyone uses auto-join to connect then they are kicked. I want to disable the option to auto-join from the game. How would I do that? Or can you fix the program so that people can still use auto-join?

Thanks.

[Enforcer]

OK, I have this thing up and running on two seperate servers and all is well so far except for on the third server. We rented a server from a company that uses Linux.

Linux thats the best what can happen :D


I connect using the ftp option. No matter what I do I can't seem to get access to the qconsole.log file. When joining the server and doing a "rcon password path" command this is what I get back:


/home/mohaa/.mohaa/main
/home/mohaa/main
/home/mohaa/main/zzz_dogmeat_multi_map_fix.pk3
/home/mohaa/main/pak6.pk3
/home/mohaa/main/pak5.pk3
/home/mohaa/main/pak4.pk3
/home/mohaa/main/pak3.pk3
/home/mohaa/main/pak2.pk3
/home/mohaa/main/pak1.pk3
/home/mohaa/main/pak0.pk3
handle1: qconsole.log

What is that handle1: qconsole.log and where the heck is it on the server? It looks like the file is being created but I have no access to it.

You should use SSH access if you have an login. Thats mutch better than the FTP.


- Added cvar: fs_userpath ... defaults to $HOME/.mohaa ... this is used to
load files, in addition to the standard fs_basepath.
- Added cvar: fs_outputpath ... defaults to $HOME/.mohaa ... this is where
files (logs and such) will be written to, since, unlike Windows, the
basepath may not have write permissions. This can be different than the
userpath, but generally you set these to be the same.
- Added cvar: logfilename ... defaults to "qconsole.log" ... use it, along
with fs_outputpath, to put your logfiles somewhere else.
If you set fs_outputpath to "/usr/local/mohaa" and logfilename to "moh.log"
then it will be written to /usr/local/mohaa/main/moh.log ...
- Added command: writeconfig <filename> ... will write out some relevant
cvars to {fs_outputpath}/main/config/<filename>.
- Added cvar: sv_chatter ... defaults to 0 ... set to 1 to see player's
chat messages on the server console. You do _NOT_ need to set the
"developer" cvar for this to work!
- Added cvar: sv_debuggamespy ... defaults to 0 ... set to 1 see information
going to and coming from gamespy...If you aren't showing up in the server
browser, enable this and see if anything is happening. (This cvar is in the
win32 version, too, but doesn't print anything.)


this is to be read in the Linux Server readme - so i thing that clear that questions


That is the problem with our main server that I am trying to fix the second problem that I have is with the auto-join function and tk monitoring. It works but if anyone uses auto-join to connect then they are kicked. I want to disable the option to auto-join from the game. How would I do that? Or can you fix the program so that people can still use auto-join?

;-)
Fix what should i fix ? Ask EA why there have done it that way. You are not able to seee what team someone is in if he use autojoin - so thats the Problem. Maybe we can fix that Problem with the AntiCheat becouse than i have a piece of my Software running at the Client also. And so far as i know im able to detect the teams than. But more later.

If you write a mod, or somebody else that would be cool. I dont know how to do so just get something working and please also write me a mail about it if you have something.
The mod _only_ have to bring the team join messages to the Server, also if someone uses autojoin, or just diable the autojoin option.


Enforcer

[captain_trips]

Ok, thanks for the reply and we are starting to get somewhere here. I found the qconsole.log file and SW can now access it. But, now the tk monitoring isn't working. I still have the serverwatch config setup the same but tk, and other features that use the log file are not working. It almost seems to me that the server isn't writing all of the data to the logfile that it needs. I still see chat info and status cmds but that is all and SW still allows me to auto-join without kicking and I can tk if I join a team.

Here is how the mohaa_lnxded cmd line is launched:

./mohaa_lnxded +set net_IP 0.0.0.0 +set ttycon 0 +set developer 2 +set sv_chatter 1 +set chat 1 +set logfile 3 &> /.mohaa/main/qconsole.log +exec server.cfg

The set net_IP and set ttycon settings are there from the server provider. I didn't want to mess up anything that they had set so I left those. Why won't tk monitoring work now? Anyone got a clue?

[Enforcer]

./mohaa_lnxded +set net_IP 0.0.0.0 +set ttycon 0 +set developer 2 +set sv_chatter 1 +set chat 1 +set logfile 3 &> /.mohaa/main/qconsole.log +exec server.cfg


+set dedicated 2 +set sv_chatter 1 +set chat 1 +exec mkf.cfg +set developer 2 +set logfile 3

Is working for me.

I also have that lines in the Config file. But i dont remember what is really needed.

set developer 2
set chat 1
seta sv_chatter 1
seta logfile 3
seta g_logsync 1

Enforcer

[captain_trips]

Got it. I just went ahead and redid all of my cfgs and deleted the origianl qconsole.log file. Rebooted the server and all is well. ServerWatch is now acting exactly like it should. Thanks for a great program.

Now, if I can figure out how to remove the option for auto-join then I'd be real happy. I'll keep looking for a way to do that.

[CobraEF]

We will have fiext that in a short time.

The new anticheat will fix that problem with autojoin.

[Green_Falcon]

uhhh, but the anti cheat will force everyone to connect with serverwatch right???

[Enforcer]

uhhh, but the anti cheat will force everyone to connect with ServerWatch right???

Ho so you mean that ? ServerWatch is reacting as Server - its the same as with the ServerWatch Client

The great difference:
Anticheat can be running in the background all the time, and if you are connection to a server what has AntiCheat installed it will connect _automatically_ without that you have to do anything.

We have an internal release at the moment - and i can say its running fine :D

[Capt_Obvious]

Would you like another BETA tester for the new version? :D :D