The Call of Duty 4 B3 RCON tool stops responding to commands in-game. Depending on the situation, it may still shows the RCON tool is running.
Example(s)
Situation #1
When restarting the B3 RCON service via the following Linux command:
sudo systemctl restart b3ffa.service
It prints to the server it is running, but it doesn't respond to any commands.
Situation #2
It doesn't print anything when attempting to restart the service via Linux.
Cause(s)
Situation #1
A lot of times this is caused by the CoD 4 log file exceeding a little over 2 GBs in size. I believe there is a file size limit for the CoD 4 log file when working with B3 RCON.
Situation #2
There is a configuration error or machine-level issue. For example, the server's RCON password was changed but wasn't updated in /var/b3/conf/<serverShortName/<serverShortName>.xml.
Solution(s)
Situation #1
There are two solutions to this. One was tested and works, the other hasn't been tested (but it should technically work).
Solution one involves logging into the server via SFTP/FTP or the File Manager feature within Pterodactyl's control panel, going to /.callofduty4/main/, and deleting the games_mp.log file. After this is done, restart the CoD 4 server itself and the B3 RCON tool. This solution requires the CoD 4 server to be restarted since it won't create a new log file until it is restarted. This solution has been tested and confirmed working.
Solution two can only be done by somebody that has access to the machine itself. Find the Docker UID of the CoD 4 server and go to /srv/daemon-data/<CoD4DockerUID/.callofduty4/main and type the following command:
sudo echo > games_mp.log
This solution hasn't been tested yet but technically speaking, it shouldn't delete the log file. Therefore, the CoD 4 server itself may not even require a server restart.
Situation #2
Check if B3 RCON configuration for the specific server and ensure the it is correct (especially the RCON password). If it still doesn't work after restarting the B3 RCON service AND the CoD 4 server itself, contact a Director and have them ensure nothing was changed on the server's back end (e.g. firewall).
Additional Information
The next time situation #1 occurs, I will be testing solution #2 to see if this fixes the issue without requiring a CoD 4 server restart.
Recommended Comments
There are no comments to display.