Frontpage   Releases   Forum   Documents   Downloads   Links   Join Us!   Disclaimer   Contact Us


Author Topic: USL Parser problems  (Read 2031 times)

0 Members and 1 Guest are viewing this topic.

Offline =VARP=Gec

  • DF Server Admins
  • Junior Member
  • *
USL Parser problems
« on: November 11, 2010, 03:20:38 PM »
sometimes parser gets Not Responsive after mission change.

I'm running this server on the Windows Server 2008, core 2 CPU 2x 1.8GHz and 4GB of RAM. It brings one core to 100% and the window is not refreshing any more. sometimes it goes back to normal after 10-20 seconds but sometimes just stays stuck like that and needs to bee killed in the process tree.

any idea where to search for problems?

Offline =VARP=Gec

  • DF Server Admins
  • Junior Member
  • *
Re: USL Parser problems
« Reply #1 on: November 11, 2010, 03:49:12 PM »
i've tried rotating all the missions and parser froze again after one mission. it came back after few minutes. the mission genereted a lot of
Code: [Select]
com.maddox.il2.objects.buildings.Plate
java.lang.ClassCastException: com.maddox.il2.objects.buildings.Plate
at com.maddox.il2.objects.buildings.HouseManager.<init>(HouseManager.java:216)
at com.maddox.il2.game.Mission.loadHouses(Mission.java:2333)
at com.maddox.il2.game.Mission._load(Mission.java:874)
at com.maddox.il2.game.Mission.load(Mission.java:817)
at com.maddox.il2.game.Mission.load(Mission.java:733)
at com.maddox.il2.game.Mission.load(Mission.java:717)
at com.maddox.il2.game.Mission.load(Mission.java:712)
at com.maddox.il2.game.cmd.CmdMission.exec(CmdMission.java:65)
at com.maddox.rts.CmdEnv.exec(CmdEnv.java:601)
at com.maddox.il2.game.DServer.loopApp(DServer.java:167)
at com.maddox.il2.game.Main.exec(Main.java:436)
at com.maddox.il2.game.DServer.main(DServer.java:431)
com.maddox.il2.objects.buildings.Plate
java.lang.ClassCastException: com.maddox.il2.objects.buildings.Plate
at com.maddox.il2.objects.buildings.HouseManager.<init>(HouseManager.java:216)
at com.maddox.il2.game.Mission.loadHouses(Mission.java:2333)
at com.maddox.il2.game.Mission._load(Mission.java:874)
at com.maddox.il2.game.Mission.load(Mission.java:817)
at com.maddox.il2.game.Mission.load(Mission.java:733)
at com.maddox.il2.game.Mission.load(Mission.java:717)
at com.maddox.il2.game.Mission.load(Mission.java:712)
at com.maddox.il2.game.cmd.CmdMission.exec(CmdMission.java:65)
at com.maddox.rts.CmdEnv.exec(CmdEnv.java:601)
at com.maddox.il2.game.DServer.loopApp(DServer.java:167)
at com.maddox.il2.game.Main.exec(Main.java:436)
at com.maddox.il2.game.DServer.main(DServer.java:431)
com.maddox.il2.objects.buildings.Plate
java.lang.ClassCastException: com.maddox.il2.objects.buildings.Plate
at com.maddox.il2.objects.buildings.HouseManager.<init>(HouseManager.java:216)
at com.maddox.il2.game.Mission.loadHouses(Mission.java:2333)
at com.maddox.il2.game.Mission._load(Mission.java:874)
at com.maddox.il2.game.Mission.load(Mission.java:817)
at com.maddox.il2.game.Mission.load(Mission.java:733)
at com.maddox.il2.game.Mission.load(Mission.java:717)
at com.maddox.il2.game.Mission.load(Mission.java:712)
at com.maddox.il2.game.cmd.CmdMission.exec(CmdMission.java:65)
at com.maddox.rts.CmdEnv.exec(CmdEnv.java:601)
at com.maddox.il2.game.DServer.loopApp(DServer.java:167)
at com.maddox.il2.game.Main.exec(Main.java:436)
at com.maddox.il2.game.DServer.main(DServer.java:431)
com.maddox.il2.objects.buildings.Plate
java.lang.ClassCastException: com.maddox.il2.objects.buildings.Plate
at com.maddox.il2.objects.buildings.HouseManager.<init>(HouseManager.java:216)
at com.maddox.il2.game.Mission.loadHouses(Mission.java:2333)


i mean really a lot. and it seams to me that parser goes through every single line and that's what keeps it busy.
the mission works ok.

for now i'll remove it from the cycle till the problem is solved.

Offline =VARP=Gec

  • DF Server Admins
  • Junior Member
  • *
Re: USL Parser problems
« Reply #2 on: November 12, 2010, 07:58:35 AM »
here is one more problem. may be it is related to the first one.

i've left the parser to work over night. this morning checked it again. i can see on the Connect tab that it is connected and working. Same thing with Mission Log tab. But if i go to Event Log tab and click Refresh i get The parameter is incorrect error.


Offline =VARP=Gec

  • DF Server Admins
  • Junior Member
  • *
Re: USL Parser problems
« Reply #3 on: November 16, 2010, 09:01:30 AM »
ok, i've found a problem and the parser works good now.

if u look on my confs.ini file

Code: [Select]
[NET]
speed=8000
serverChannels=120
localPort=21000
SkinDownload=1
difficulty=26998271
serverName= =VARP= ft. Gec's dedicated server
serverDescription=UP 2.01 - USL addon, powered by IL2 Daemon, stats @ http://gec.servebeer.com/stats
checkServerTimeSpeed=1
checkClientTimeSpeed=0
socksHost=

[chat]
autoLogDetail=3

[MaxLag]
farMaxLagTime=10.0
nearMaxLagTime=2.0
cheaterWarningDelay=10.0
cheaterWarningNum=3

[Console]
IP=21003
IPS=192.168.100.100
LOG=1
LOGTIME=1
LOGFILE=eventlog.lst
HISTORY=128
HISTORYCMD=128
LOGKEEP=1

[rts]
ProcessAffinityMask=2

u'll see that i've put eventlog.lst as my event log file in the [console] section

Code: [Select]
[Console]
IP=21003
IPS=192.168.100.100
LOG=1
LOGTIME=1
LOGFILE=eventlog.lst
HISTORY=128
HISTORYCMD=128
LOGKEEP=1

i was sure that that was same thing as
Code: [Select]
[game]
eventlog=Eventlog.lst
eventlogkeep=1
so i've deleted the [game] section to not to have double statements.

but that was wrong!!

one needs to have [game] section defined in order the IL"Daemon, IL"Stats or FBDj to work properly and the LOGFILE defined in the [console] section needs to have different name. default is logs.lst

just for anyone else who would do the same mistake.

Offline =VARP=Gec

  • DF Server Admins
  • Junior Member
  • *
Re: USL Parser problems
« Reply #4 on: November 16, 2010, 12:48:24 PM »
Here is a new problem. stats are displayed with timestamp 2 hours behind actual time. is there a clock that needs to be set?

OC system clock shows good time.

Offline Pappy

  • Global Moderator
  • IL2 Addict
  • ******
Re: USL Parser problems
« Reply #5 on: November 16, 2010, 02:18:03 PM »
That is a new one.  It should be using the system time.  But I seems there is an issue.

I do not have time to work on the code now.  I'll see what I can do with it in the future.

I appreciate you pointing out these bugs.

Offline =VARP=Gec

  • DF Server Admins
  • Junior Member
  • *
Re: USL Parser problems
« Reply #6 on: November 16, 2010, 03:06:21 PM »
what is interesting is that the time in eventlog is one hour behind system clock. and the time that parser shows on the web is one extra hour behind. in total 2 hours.

main question is how the server gets the time

Offline Pappy

  • Global Moderator
  • IL2 Addict
  • ******
Re: USL Parser problems
« Reply #7 on: November 17, 2010, 03:14:59 PM »
The Parser gets the time from the log file.  The one hour difference between the parser and the log file may be an issue with day light savings time.

I do not recall seeing this issue in the USL last season.

 

Powered by EzPortal