04-02-2012, 05:28 PM
Hello,
we had problems with our servers visibility on the master serverlist. We basically had no idea were the problem laid, but we may have progressed a little bit.
The server is a dedicated server, hosted by a service provider. Kernel is compiled by one of us.
Symptoms that we had first:
The servers would be shown in master serverlist and in hlsw for about 1 -2 minutes and then go offline, but in fact the were online. We could connect to them with "connect <ip>" from console, but sometimes this resulted in "STEAM validation rejected" error note. I also noticed that bots were running a bit faster on this server, also the connection time of bots was jumping around randomly in hlsw when the servers were started.
What fixed this problem, was that I added "export RDTSC_FREQUENCY=disabled" to the startup script. This corrected the errors above.
What I would like to know is, where do you think the problem is? Kernel? Is there an instability risk with starting the server with the command above? The server was inaccessible for about 15 min yesterday after I had added this command, could it be because of the command above?
I would also like to apologies for the spelling and bad English. Sorry
we had problems with our servers visibility on the master serverlist. We basically had no idea were the problem laid, but we may have progressed a little bit.
The server is a dedicated server, hosted by a service provider. Kernel is compiled by one of us.
Symptoms that we had first:
The servers would be shown in master serverlist and in hlsw for about 1 -2 minutes and then go offline, but in fact the were online. We could connect to them with "connect <ip>" from console, but sometimes this resulted in "STEAM validation rejected" error note. I also noticed that bots were running a bit faster on this server, also the connection time of bots was jumping around randomly in hlsw when the servers were started.
What fixed this problem, was that I added "export RDTSC_FREQUENCY=disabled" to the startup script. This corrected the errors above.
What I would like to know is, where do you think the problem is? Kernel? Is there an instability risk with starting the server with the command above? The server was inaccessible for about 15 min yesterday after I had added this command, could it be because of the command above?
I would also like to apologies for the spelling and bad English. Sorry
Code:
GCC -v
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.4.5-8' --with-b ugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran ,objc,obj-c++ --prefix=/usr --program-suffix=-4.4 --enable-shared --enable-multi arch --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without -included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++ /4.4 --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debu g --enable-objc-gc --with-arch-32=i586 --with-tune=generic --enable-checking=rel ease --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.4.5 (Debian 4.4.5-8)
ldd --version
ldd (Debian EGLIBC 2.11.3-3) 2.11.3
uname -v
#3 SMP PREEMPT RT Sun Feb 19 22:14:37 EET 2012
uname -a
2.6.33.7-rt29 #3 SMP PREEMPT RT Sun Feb 19 22:14:37 EET 2012 x86_64 GNU/Linux