Situation #1
HLStatsX is completely down for a server both in-game and on the web portal.
Situation #2
HLStatsX is down only in-game. But is updating on the web portal.
Example(s)
Situation #1
The rank won't show in-game and on the web portal it shows nobody is connected to the server and isn't tracking any player's stats.
Situation #2
On the web portal it shows players are connected and is tracking statistics properly. However, the menu in-game is not popping up after multiple attempts.
Cause(s)
Situation #1
There can be multiple causes to this issue. Let me go over the common causes.
Cause #1
The daemon the server is reporting to is down. If you have the proper access to the daemons through Linux, you can execute the following command while in the HLStatsX directory to see the status of the daemons.
./run_hlstats status
If all the daemons are up, it should output:
HLstatsX:CE daemon control http://www.hlxce.com --------------------------- Daemon on port 27500 is currently running. Daemon on port 27501 is currently running. Daemon on port 27502 is currently running. Daemon on port 27503 is currently running. Daemon on port 27504 is currently running.
It will say if one of the daemons are down in the output above.
Cause #2
The server isn't logging to the HLStatsX daemon. To check this, you should execute the following command on the server:
logaddress_list
This will output all the IPs and ports the server is logging to. It should have the website's IP followed with the daemon's port in here. If not, please contact @Roy to get the details.
Situation #2
In the case that the HLStatsX plugin is actually loaded, the following could be the causes to the issue.
Cause #1
Normally, this is due to an incorrect RCON password stored in the HLStatsX admin panel.
Cause #2
The server may have blocked the website's IP which is used to send information to the game server. You can check what IPs are blocked by executing the following command on the server:
listip
The website's IP is normally 192.99.230.204. The reason the IP may be blocked is because something is requesting the server through RCON with an incorrect password (e.g. SourceBans). You may have to contact a tech from GFL to further investigate this issue if that is the case.
Solution(s)
Situation #1
Solution #1
Since one or more of the daemons are down, they will need to be restarted. If you have the proper access, you can achieve this with the following command:
./run_hlstats restart
This will attempt to shut down any daemons still up and restart all daemons.
If a daemon is down, I would highly recommend checking the HLStatsX logs if you have proper access. This is in the logs/ directory within the HLStatsX installation. For example, logs/hlstats_27504_2018-10-16_12-20-01. Something likely crashed the daemon (e.g. MySQL error, etc.).
Solution #2
Since the game server isn't reporting to any daemons, you will need to have it log to our HLStatsX daemons. You can just add the following to your server.cfg file more than likely:
logaddress_add hlstats.gflclan.com:27503
In this case, it uses port 27503. However, you can use the port range 27500 - 27504. These are the ports opened for us right now and it will remain this way more than likely.
Situation #2
Solution #1
If you have access to the HLStatsX admin panel, you can login and edit the server's RCON password to the correct one. This may involve a daemon restart and Situation #1 -> Solution #1 goes over how to restart the HLStatsX daemons if you have proper access.
Solution #2
Anybody with server RCON/server console access can remove the IP from the banned list by executing the following:
removeip 192.99.230.204
It may also be worth to put this in your server.cfg so it automatically removes the IP from the banned list on map change. Keep in mind, it would be best to figure out why the website's IP is being banned in the first place. Therefore, it may be worth asking somebody to investigate this if you can't figure it out yourself. Remember, SourceBans trying to perform RCON commands with an invalid password to the server is a common cause to this issue.
Additional Information
None.

Recommended Comments