6 TroubleshootingThis section handles a number of trouble shooting issues, which can cause problems with a correct functioning of Globule and instructions on how to overcome obstables in some cases. 6.1 Compatibility with other Apache modules and settingsIn general, Globule is well-behaved and follows the Apache interface. However, some modules or configurations can clash. Most incompatibilities with other modules and settings emerge because the same environment as the origin server cannot be emulated on the replica host. This section surveys a number of them. 6.1.1 Modules that won't workThe usage of the following modules will not work when the modules are active on the web-site being replicates. This means that the modules can be used within the same server that runs Globule, just not on a web-site that is Globule replicated:
6.1.2 Constructions that won't workThe following Directives and constructions will not operate well with Globule.
6.2 System resource usageIn Linux, if Apache/Globule crashes, it sometimes does not deallocate the semaphores used for process synchronization. Restarting the server may then fail because it cannot allocate sufficient semaphores. You can cleanup all semaphores using: ipcrm `ipcs -s | awk '(int($2)>0){print"-s",$2}'` Use with care, especially when running as root as this will release all semaphores, also ones still in use by other programs (X windows amongst others). 6.2.1 Allow high quantities of shared memory in your operating systemYour operating system must be configured to support the amount of shared memory specified in directive GlobuleMemSize. You can check and set this as follows:
Linux:
Solaris:
6.2.2 Allow large numbers of locks in your operating systemYour operating system must be configured to support the number of locks specified in directive GlobuleLockCount. You can check and set this as follows: Linux:
Solaris:
June 29, 2006 |