April 5, 2012 at 12:08 am #273
Do you happen to know if it is occurring just prior to a new player joining the server?
There are also a few debug statements that I can try removing for the next build.
PhreezeApril 5, 2012 at 11:32 am #276
Good point, I don’t know but I will keep an eye on it to try and see.April 6, 2012 at 3:06 pm #285
We seem to have a problem with the BanUserList.txt file. We had 17 entries yesterday, today we have only 2 and they were both banned today. The server has not been restarted for 2 days 20 hours and it is highly unlikely that any member has cleared the list. That’s the only information I have for now.April 6, 2012 at 5:10 pm #286
I don’t suppose you have a copy of the console logs and/or original BanUserList.txt before it was wiped out?
In any case, since these issues will be difficult to debug, I’m going to try and implement a few things that will assist us. 1) server console output should also log to a file (windows version really needs this anyways), 2) generate backup copies of the ban list files whenever updating them, and 3) check the # of bans after a scmd banuser or unbanuser command to ensure the count has only increased or decreased by 1, otherwise do not save to disk.April 6, 2012 at 5:47 pm #287
As far as I am aware the Windows version doesn’t keep a copy of the console logs! But I do have a copy of the original BanUserList.txt file and the current one in which I have now added the original entries. I have e-mailed you both.April 8, 2012 at 6:00 pm #408
Something is up with our servers:-
[[RaW]zelk0wy] [INFO]: Client connected
[2012-04-08 18:57:17] [188.8.131.52:32779] [51.5ms] [[RaW]zelk0wy] [ERROR]: Invalid client message type received before client passed security! (Message ID = 245)
It’s happening on all SEC2 servers.April 8, 2012 at 6:17 pm #409
hmmmm that’s something that looks like a problem.
We will check that asap :OApril 8, 2012 at 6:30 pm #410
It’s all O.K. now and I can access all SEC2 servers.April 9, 2012 at 1:18 am #412
I still wonder If that happened to other servers, I didn’t test.April 9, 2012 at 10:34 am #415
Yes it happened on all servers running SEC2. It obviously didn’t affect players already in the servers, just those joining. Our server was low on players so I tried to join our server, zelk without me knowing was doing the same thing, we both got the same result which was just the loading screen and map name and there it hung, that’s when I went into VNC and saw the error messages.
We tried our other servers, then other clan’s servers running SEC2 including mxt, all with the same result, then I managed to get into mxt and at that same time players managed to get in to our server, so I would say it lasted for around 8-10 minutes in all.April 9, 2012 at 3:48 pm #416
but I mean other FEAR (nonSEC2) Servers.April 9, 2012 at 11:30 pm #417
No, I could get into those without any problems, so I was just about to reboot into the old SEC when SEC2 started working again.April 10, 2012 at 1:56 am #418
I think I might have an idea of what happened. Apparently there was an unplanned gamespy outage, and looks like SEC2 is not handling the server exception in the exact same way as original FEAR/SEC. I’m going to change the exception handling to error more on the side of caution when receiving an “invalid” response from gamespy and let the players in.
Unfortunately it is hard to test because gamespy keeps ignoring my requests to bring down their servers so that I can test SEC2 error handling!April 28, 2012 at 6:47 pm #547
The following are tested and working in Beta5:
cmd_warnuser [ID] Player has been issued a warning1 (Reason Warned by admin). Is it possible that we could put an actual reason in there?
These are both very handy for getting players attention, would it be possible to have something like: cmd_burn2 & cmd_fry2 where it takes 50% of players health?
Along with a few new significant features. Should be released within a few days after internal testing is completed.April 28, 2012 at 11:14 pm #548
Thanks Phreeze, good work m8. I look forward to seeing this.
You must be logged in to reply to this topic.