For all that are browsing these forums wondering about your Source server: (you should have also received an email with this same information)
Valve released a Source update today at around 2:45pm PST. We downloaded the update at that time and attempted to apply it, but it would not work. After contacting Valve, we were told the problem was a result of a bug in their Steam updatetool software. So, we redownloaded the updates and then rolled them out to all our servers. This unfortunately took another hour or so because at that point the Steam content servers were overutilized.
Now, after we applied the update to all our servers, we have discovered that the update breaks multihoming (the ability to assign more than one IP address to a machine and choose which one the game server uses when it starts up). Our systems require multihoming support. Without it, all our servers are running on random ports, on random IP addresses. This makes them difficult to find and impossible for our systems to track.
We have again contacted Valve on this latest problem. As soon as Valve releases another update that fixes it, we will apply it and restart all our Source servers.
------------------------------------------------------------
CounterStrike:Source Server Update -- READ THIS
- bOoya
- Former staff
- Posts: 886
- https://www.youtube.com/channel/UC40BgXanDqOYoVCYFDSTfHA
- Joined: Thu Jan 15, 2004 3:46 pm
- Location: Corona, CA
- Contact:
Valve's dragging its feet on this issue. At this point we are not anticipating a fix today.
The current workaround is to find your temporary IP/port in the Steam browser or using a tool such as game tiger, then using that to connect to the server.
As soon as Valve releases a patch, we will roll it out to our servers and the IPs and ports will change back to the usual ones.
The current workaround is to find your temporary IP/port in the Steam browser or using a tool such as game tiger, then using that to connect to the server.
As soon as Valve releases a patch, we will roll it out to our servers and the IPs and ports will change back to the usual ones.
I could really go off on a tangent over the issue, but I will refrain from doing so. Let's just say that I am incredibly disappointed and angry over this problem...Edge100x wrote:Valve's dragging its feet on this issue. At this point we are not anticipating a fix today.
The current workaround is to find your temporary IP/port in the Steam browser or using a tool such as game tiger, then using that to connect to the server.
As soon as Valve releases a patch, we will roll it out to our servers and the IPs and ports will change back to the usual ones.
Aye. It has made everyone's afternoon and evening a living hell.
Everything was going so well on Thursday before Valve released this patch, too.
I wish they had taken this bug seriously and fixed it Thursday. It seems they decided it wasn't important enough, and went home for the night, leaving the rest of us hanging.
It should be a very easy-to-fix bug.
I would suspect it has something to do with "Fixed network being started early enough so UDP remote logging works" in the changelog. They probably start the network too early now.
Everything was going so well on Thursday before Valve released this patch, too.
I wish they had taken this bug seriously and fixed it Thursday. It seems they decided it wasn't important enough, and went home for the night, leaving the rest of us hanging.
It should be a very easy-to-fix bug.
I would suspect it has something to do with "Fixed network being started early enough so UDP remote logging works" in the changelog. They probably start the network too early now.