Table of Contents
While we attempt to prevent problems from occuring duting the installation process, some will inevitably arise. This appendix aims to outline some of the more common failure cases that can occur when installing the BigWorld server and tools.
-
To check if the daemon is running, use control_cluster.py[3] utility. To use control_cluster.py to check the status of BWMachined, issue the following command:
$ bigworld/tools/server/control_cluster.py cinfo
The machines correctly running BWMachined should be displayed, as in the example below:
shire 10.40.3.37 0 processes 0%, 0% of 2000MHz (4% mem)
Make sure that the process has an address that is on the internal network. If it does not, make sure that your broadcast route is set correctly.
If your machine is not listed, but has BWMachined running, then you might need to check your firewall rules. For more details, see section Security in this document.
You can also run the following command to check the relationship between bwmachined processes in the cluster.
$ bigworld/tools/server/control_cluster.py checkring
Some of the most common problems that can occur when installing a BigWorld service are a result of BWMachined not running after the initial installation. The following outlines the most common issues encountered and how to resolve these problems. These steps should be checked in order.
-
Is BWMachined running?
/sbin/service bwmachined2 status
If BWMachined is running, you may have to adjust firewall rules in order to allow UDP broadcast messages to be sent and received around the server cluster. For more information please refer to Security.
If BWMachined is not running, continue with the following step.
-
Was BWMachined able to start at all?
BWMachined is quite often able to successfully startup but will then fail when attempting to send broadcast messages out to the network. In order to determine what happened on startup we need to investigate the system logs (syslog) which can be found by default in
/var/log/messages. Output from a successful startup should appear as follows:/opt/bigworld/2.1/bwmachined/sbin/bwmachined2: --- BWMachined start --- /opt/bigworld/2.1/bwmachined/sbin/bwmachined2: Host architecture: 64 bit. /opt/bigworld/2.1/bwmachined/sbin/bwmachined2: Using gettime timing /opt/bigworld/2.1/bwmachined/sbin/bwmachined2: Broadcast discovery receipt from 10.40.3.145. /opt/bigworld/2.1/bwmachined/sbin/bwmachined2: Confirmed 10.40.3.145 (eth0) as default broadcast route interface.
The key line here is the final line that confirms the default broadcast route. If you do not see this line and in its place see an error message you will most likely need to adjust the default broadcast routing rules. For more details see Routing.
If you are having trouble finding BWMachined output in your syslogs, try restarting BWMachined which should generate new logs as it starts.
Some of the most common issues encountered with StatLogger include:
-
Incorrect or no MySQL database connection info provided.
This can be resolved by following the instructions outlined in Configuring StatLogger.
-
Old versions of Python MySQLdb module being used.
This issue will generally manifest itself as StatLogger failing to reconnect to the MySQL server overnight when the StatLogger service is not being heavily loaded.
This issue can be resolved by installing the Python MySQLdb module provided by BigWorld as outlined in BigWorld Server Tools.
When all else fails and you are uncertain of how to procede, contacting BigWorld support is the next step. BigWorld provides a number of support methods.
For Indie package customers, using the forums is the best place to ask questions. The forums are located at https://forum.bigworldtech.com. These forums are a community interaction with other Indie customers who have most likely encountered the same issues as you. BigWorld staff do monitor and respond to these forums.
For non-Indie customers, using the PerlDesk ticket system available at http://support.bigworldtech.com is the recommended method of asking questions. This ticketing system allows us to track questions and ensure that they are responded to in a timely manner.