Version pré-compilée pour Ubuntu 16.04 : Ubuntu PPA
Notes › Informatique › Hacks
dimanche 23 juin 2013
Compiler Kurso de Esperanto version 4 sous Debian et Ubuntu depuis les sources
Par Mathieu le dimanche 23 juin 2013, 14:37
jeudi 23 mai 2013
Install Counter Strike: Source server using SteamCMD on Linux (and get rid of MasterRequestRestart)
Par Mathieu le jeudi 23 mai 2013, 18:37
You may have noticed that the legacy HLDSUpdateTool, is deprecated for a while. Since the recent udpate from Steam that forces all CSS clients to use the new SteamPipe system, the server downloaded by HLDSUpdateTool is definitely deprecated.
If you try to run a deprecated version of your server (acquired with HLDSUpdateTool), you will get one of the following :
MasterRequestRestart
Your server is out of date. Please update and restart.
MasterRequestRestart
Server will restart on map change.
And the client is getting the following :
The server you are connecting to is running an older version of the game
You can try to update using HLDSUpdateTool but nothing will change, you will be stuck with your old version, and you will keep getting the same errors.
The key is to get the new CSS server software, that uses SteamPipe. To do so, you have to grab the new SteamCMD program, that replaces HLDSUpdateTool, and install the CSS server as explained in Valve documentation.
Here is a few-steps tutorial to install your new CSS server :
- Make sure you create a new directory for SteamCMD files, do not install it in HLDSUpdateTool directory :
mkdir steamcmd && cd steamcmd
Download SteamCMD :
wget http://media.steampowered.com/client/steamcmd_linux.tar.gz
Extract SteamCMD :
tar -xzf steamcmd_linux.tar.gz
If you are running a 64bit system (every decent server does), install ia32-libs (for instance, in Debian :
dpkg --add-architecture i386 && apt-get install ia32-libs
).Run SteamCMD :
./steamcmd.sh
it will update automatically.Install CSS dedicated server, in a custom directory (here it’s the folder css_server in upper directory) :
./steamcmd.sh +login anonymous +force_install_dir ../css_server/ +app_update 232330 validate +quit- Note that the Steam AppID is 232330.
Now you can run your new CSS server : get back to the upper directory (
cd ..
) and start it :
./css_server/srcds_run -steam_dir steamcmd/ -steamcmd_script steamcmd/steamcmd.sh -console -game cstrike +map de_dust2 -maxplayers 20 -port 27015
Of course, you will have to copy your existing server.cfg, mapcycle, and MODs to your new CSS installation directory (in css_server/cstrike/
sub-folders).
I hope this post will help those who are stuck with these “server deprecated” errors and unable to use their server. Have fun !
mardi 21 mai 2013
Install Counter Strike dedicated server (Source, Condition Zero, Global Offensive) using SteamCMD on Linux
Par Mathieu le mardi 21 mai 2013, 22:07
It is not recommended anymore to use HLDSUpdateTool to set up and update your Counter Strike server, it will give you a deprecated version of the server since Valve has moved his games to SteamPipe.
I will explain in this short tutorial how to set up your Counter Strike server using the new Valve bootstrap: SteamCMD.
Step 1: Your server
I am making the assumption that you have a dedicated server (virtual or not), with shell and root access. If you don't have root access, I assume that you have at least shell access, possibility to open ports, and 32bit libraries installed.
Step 2: Prepare install
Follow this if you have root access, otherwise continue to step 3.
-
Install 32bit libraries:
-
For Debian/Ubuntu:
dpkg --add-architecture i386 && apt-get install ia32-libs
-
For Fedora/RHEL/CentOS:
yum install glibc.i686 libstdc++.i686
-
For Arch:
Enable Multilib and then type:
pacman -S lib32-gcc-libs
-
-
Make a new user and "su" it:
adduser --disabled-login steam
su steam
cd /home/steam -
You should NEVER run a server with root user, every time you want tot start your server, do a "
su steam
" or log in with this user before. If you want to log in with the steam user, remove the--disabled-login
from command line when creating it.
Step 4: Download and install SteamCMD
- Create a new directory and use it as your current directory:
mkdir steamcmd && cd steamcmd
-
Get the SteamCMD binary:
wget http://media.steampowered.com/client/steamcmd_linux.tar.gz
- Extract the tarball:
tar -xzf steamcmd_linux.tar.gz
-
Run the steamcmd binary, it will update:
./steamcmd.sh
Step 5: Download the Counter Strike server
The command line will force the installation directory in a separate directory. It prevents messing with SteamCMD directories when you configure and start the game server.
For Counter Strike Source:
./steamcmd.sh +login anonymous +force_install_dir ../css_server/ +app_update 232330 validate +quit
For Counter Strike Condition Zero:
./steamcmd.sh +login anonymous +force_install_dir ../cscz_server/ +app_update 90 +app_set_config 90 mod czero validate +quit
For Counter Strike Global Offensive:
./steamcmd.sh +login anonymous +force_install_dir ../csgo_server/ +app_update 740 validate +quit
Of course, you can change the name of the installation directory. Just don't forget the ../
before the folder name to install it in the upper directory, otherwise you will mess your SteamCMD installation with game files.
Use the same command to update your server when needed.
Step 6: Configure your server
I can't learn you anything here: just place your server.cfg, mods, and maps accordingly in the installation folder.
Step 7: Start your server
-
Get back to the steam user home directory
cd /home/steam
-
Start the server:
-
For Counter Strike Source:
./css_server/srcds_run -steam_dir steamcmd/ -steamcmd_script steamcmd/steamcmd.sh -console -game cstrike +map de_dust2 -maxplayers 20
-
For Counter Strike Condition Zero:
./cscz_server/srcds_run -steam_dir steamcmd/ -steamcmd_script steamcmd/steamcmd.sh -console -game czero +map de_aztec -maxplayers 20
-
For Counter Strike Global Offensive:
./css_server/srcds_run -steam_dir steamcmd/ -steamcmd_script steamcmd/steamcmd.sh -console -game csgo -usercon +game_type 0 +game_mode 0 +mapgroup mg_bomb +map de_dust
See Valve documentation for other game modes.
-
Please adapt the command line if you changed the name of installation directory.
Step 8: Enjoy !
Again, nothing much to say, just enter your server IP address in the game.
Just one more thing: if you didn't had root access during the installation, you may have to forward ("open") ports to let your server be accessible by anyone.
mercredi 15 mai 2013
Install Team Fortress 2 server using SteamCMD on Linux (and get rid of MasterRequestRestart)
Par Mathieu le mercredi 15 mai 2013, 16:26
You may have noticed that the legacy HLDSUpdateTool, is deprecated for a while. Since the recent udpate from Steam that forces all TF2 clients to use the new SteamPipe system, the server downloaded by HLDSUpdateTool is definitely deprecated. The Team Fortress’ wiki is giving wrong informations, that procedure is deprecated.
If you try to run a deprecated version of your server (acquired with HLDSUpdateTool), you will get one of the following :
MasterRequestRestart
Your server is out of date. Please update and restart.
MasterRequestRestart
Server will restart on map change.
And the client is getting the following :
The server you are connecting to is running an older version of the game
You can try to update using HLDSUpdateTool but nothing will change, you will be stuck with your old version, and you will keep getting the same errors.
The key is to get the new TF2 server software, that uses SteamPipe. To do so, you have to grab the new SteamCMD program, that replaces HLDSUpdateTool, and install the TF2 server as explained in Valve documentation.
Because the documentation is not quite clear (in particular, concerning the new AppID to use), here is a few-steps tutorial to install your new TF2 server :
- Make sure you create a new directory for SteamCMD files, do not install it in HLDSUpdateTool directory :
mkdir steamcmd && cd steamcmd
Download SteamCMD :
wget http://media.steampowered.com/client/steamcmd_linux.tar.gz
Extract SteamCMD :
tar -xzf steamcmd_linux.tar.gz
If you are running a 64bit system (every decent server does), install ia32-libs (for instance, in Debian :
dpkg --add-architecture i386 && apt-get install ia32-libs
).Run SteamCMD :
./steamcmd.sh
it will update automatically.Install TF2 dedicated server, in a custom directory (for me it’s the folder tf2_server in upper directory) :
./steamcmd.sh +login anonymous +force_install_dir ../tf2_server/ +app_update 232250 validate +quit- Note that the Steam AppID is now 232250 and not 440 as HLDSUpdateTool used to prompt.
Now you can run your new TF2 server : get back to the upper directory (
cd ..
) and start it :
./tf2_server/srcds_run -steam_dir steamcmd/ -steamcmd_script steamcmd/steamcmd.sh -console -game tf +map cp_dustbowl -maxplayers 16
Of course, you will have to copy your existing server.cfg, mapcycle, and MODs to your new TF2 installation directory (in tf2_server/tf/
sub-folders, indeed). If you have no clue of what I am talking about, please read the Team Fortress Wiki.
I hope this post will help those who are stuck with these “server deprecated” errors and unable to use their server. Have fun !
samedi 16 mars 2013
Apache : globally configure HTTPS for all VirtualHosts
Par Mathieu le samedi 16 mars 2013, 19:16
You want to configure “once and for all” HTTPs for all domains and sub-domains handled by your webserver, and you don’t want to redeclare the certificate in each VirtualHost. Here is the trick.
I run Debian. In a default Apache installation, the directory /etc/sites-enabled contains a file named 000-default which declares a default VirtualHost for HTTP.
You have to know that when Apache loads an entire directory of configuration files, the files are read in alphabetical order. So if you want to declare something before something else, you can cheat on its name in the loaded configuration. It is exactly what 000-default does.
In /etc/apache2/sites-available, you have a file named default-ssl. Edit this file to fit your needs (path to certificate, etc). Note that this certificate will be the same for all the domains hosted on your server. It’s what we want : only one configuration. If you are hosting multiple domains on the same server, the certificate will probably be invalid for at least one of your domains, and you should use mod_macro instead of a global HTTPs configuration.
Now, enable the website the common way : a2ensite default-ssl. Don’t restart Apache yet.
Rename the file default-ssl created in /etc/apache2/sites-enabled/ to 000-default-ssl.
Configure your other VirtualHost with a *:80 section and a *:443 section, as usual but without specifying certificate and SSL informations for VirtualHosts on *:443.
If you restart Apache, you will notice something like this :
_default_ virtualhost overlap on port 443
To get rid of these warnings, just add to your ports.conf, in the right section :
NameVirtualHost *:443 Listen 443 http
When you finally restart Apache, every VirtualHost declared as *:443 will use the certificate defined in 000-default-ssl without mentioning it.
« billets précédents - page 10 de 12 - billets suivants »