Restarting the server apparently solved it. I guess it was just one of
those weird things.
On 06/08/2011 11:29 AM, David A. Parker wrote:
It happens regardless of the query tool, so there's definitely garbage
in the A2S_INFO response packet from that fork. What I can't figure out
is why it's happening only on one fork, and the other 5 are fine. This
just started happening when the server got the June 3rd updates.
I'll restart the server and see what happens.
On 06/08/2011 11:22 AM, Eric Riemers wrote:
Perhaps the way you read out the A2S_INFO is wrong. Dont know which
tool/program/etc you use right now for it, but perhaps you can use a
different one and see if its the same.
On Wed, 08 Jun 2011 11:13:38 -0400, "David A. Parker"<[email protected]>
wrote:
One more things to add... These weird characters only show up in the
A2S_INFO response. They do not show up in the output of sv_showtags:
sv_showtags
Tags:
Public : coop,empty,secure
This matches the output of sv_showtags on the other forks.
On 06/08/2011 11:09 AM, David A. Parker wrote:
Hello,
I have an L4D2 server running 6 forks. 5 of the forks have the normal
text in their tags:
coop,empty,secure
Fork #2, however, has this:
#4� ^ @coop,empty,secure
Any idea why one fork out of six would have garbage in its tag
string? I
haven't restarted the server because it appears to be working fine
otherwise. I'm just curious if anyone else has seen this, or knows what
might cause it.
Thanks,
Dave
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives,
please visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
--
Dave Parker
Systems Administrator
Utica College
Integrated Information Technology Services
(315) 792-3229
Registered Linux User #408177
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux
