This article describes various scenarios causing the slave server to go down and provides troubleshooting suggestions. If all possible causes listed have been verified and the issue persists, please contact Systemite Support at firstname.lastname@example.org. We would be happy to take a look at your swSlaveServer log file to troubleshoot.
If the network connection between the master server and the slave server goes down, the slave server will shut down and users will be unable to connect to the slave server. Verify if there has been a networking issue.
Out of Memory Error Upon Start
If the slave server starts normally, but then throws an 'Out of memory' error when it tries to load data from the master server, it may be that there is not sufficient RAM on the slave server machine. You'll want to make sure that the memory allocated to the server is at least 3 times the size of the database. For example, if the database size is 10 GB, we recommend that the slave server have 30 GB of available RAM. It may work with 2 times the size of the database, but we recommend 3 times. If LoadAllData=True is configured for the slave server in swSlaveServer.ini, the slave server will receive ALL data from the master server upon start-up. We recommend this setting since latency will be lower for users when all data is on the slave server upfront.
Master Server Down
If the master server goes down, the slave server will shut down and users will be unable to connect to the slave server. We advise that communication be sent out to all affected users when the system is taken down for planned or unplanned maintenance.