Sitting-Duc

The host has certain limitations on the file access. The bots have no way of accessing the log files on the new host (NFO). I am investigating if I can find a work around. We did try a VDS on the same host which allowed the running of the bots but because of the bad feedback we were forced to make a change. The new hosting is on a server with far superior hardware (albeit shared).

Try Fedex?

@@hxtr TF used quake, TF2 has used the source engine since 2000

I did it but I had to prioritise working on some other stuff so it's not 100% working.

Actually I kinda get what he means about the spectating thing. To try and troubleshoot any problems with the servers I have been in spectate for hours on end the past few days just watching and reading chat to see the lag complaints (they are few and far between). I have really enjoyed just watching people play

I would doubt that, it looks to be separate problems on the servers we are having problems with. Plus they are in different data centres.

Our host has supplied the following bulletin: This is affecting the 8.12.17.103:28960 >XI< Vietnam FreezeTag 1 only.

Our host has supplied the following bulletin: This is affecting the 8.12.17.103:28960 >XI< Vietnam FreezeTag 1 only.

Which server?

It is in Chicago, and to my knowledge hasn't moved in a while.

Most likely if these are host issues then they are temporary. We will just have to wait for a while to see if they get resolved. It's happened twice, I would not make the assumption of a daily occurrence. Obviously I cannot speak for the host but usual restarts are every few months - I happen to know these restarts are concerning the HDD drivers. The TOD is chosen as it is the lowest daily traffic.

Teamspeak didn't crash it was a host restart. Unsure of why the pings are up.

I have already said in the past that if you guys are having too many issues then we can revert to hosting elsewhere. At this point if you are not having much luck then the servers with problems can be moved away to a Windows server or a different game host. Now if I am getting what you guys are saying correctly (in this thread and others): 74.208.70.146:28960 >XI< Modern Weapons Mod - Running OK on Linux? 50.97.113.67:28960 >XI< DM Custom Maps - This server you are saying is having lots of issues? are they network or mod related? 74.208.70.85:28960 >XI< DM Custom Maps 2 - Having some issues? are they network or mod related? 8.12.17.103:28960 >XI< Vietnam FreezeTag 1 - Running fine? 50.97.113.65:28960 >XI< REDLINE - Running fine? Please clarify that for me so I can look at some options.

I think I'm not right for the job most of the time.. especially when it's fixing what someone else has broken which is the case here.. but then I break something myself and it just, well, feels right. So be warned because of said stressful week I will be breaking the website for a while

(Trying to keep as calm as possible because I have worked my ass off the past week) Firstly we had to decide where to go and what to do and had to read all of the complaints of the temp server and perform network tests and the like to try and find the most stable location for the servers. Then came access to our files - do any of you know how long it takes for an entire server (not a single game server) to be moved from the US to EU? well it's many TB and takes a long time. So we had to wait for our host to go through the process of meetings with the data centre and then planning when to move and then performing the actual migration. We could not access our files before then. Then once we actually had decided on a location and ordered a server it needed configuring. So the OS had to go through its updates, dependencies for the game servers installed, python, etc. Oh and the panel and linking that panel to the Master. None of these taking that long in particular or that hard to do - but collectively taking up my time. So wahoo we have a working panel and all the dependencies so then it's time to get our 200GB back from the EU to US again, which again is another click and set going - then come back the next day jobbie. At this stage we are at yesterday morning. By the evening both servers were up and running. Now I could have announced it then but there are still a few hours more work to do: Additionally through this week I have had to move house from England to Wales, work a few days to get some extra money and also take my senile (ok well getting that way) parents to Cardiff to shop for smartphones. The end result is two servers that look to be working perfectly minus the list above. 192.223.24.212:28960 >XI< NEW MW2 Freezetag www.xtremeidiots.com 192.223.27.28:28960 >XI< FreezeTag Server 1 Although even that won't please some. /end rant

Yeah you have an active PBBan against your account and will be unable to play on our servers with it. You may appeal to PBBans (in this case Evenbalance as well). You my not appeal to us.

I don't really care how people setup PB as it's the same thing in a different way, however, why are you replacing the .exe's? they are not related to PB in any way and especially as the SP version does change size I do have concerns on that. Other than that there is no difference to someone downloading the files from the downloads section on this site or from your dropbox.

Locking this thread as we have made our decision. Thanks for the input guys! A post will be made when possible with info of the new server.

Locking this thread as we have made our decision. Thanks for the input guys!

You need to do the trace until you get one which has a ping spike, that's how you find out the node with the problem.

You are looking at a trace route from the server to your computer. The final hop visible is to your current IP address which is of 340ms, the previous hop being 55ms. What I do not understand is why you are only having issues on this singular server as the trace route is displaying the final hop as the one which issues which is your own network. Could you run some trace routes to the server until you have one with a larger hop time so we can see from your end?

Found the cause:

Your lag is being caused by something in between. Pinging you from the server yields this result: There are two spikes in that short capture time which will be the problem.