"Not enough free disk space" error on PGP Universal Server when adding a cluster member
|Article:TECH195352|||||Created: 2012-08-21|||||Updated: 2013-04-29|||||Article URL http://www.symantec.com/docs/TECH195352|
Upon trying to join a cluster member into the environment. You could receive an error in the User Interface which states that the server does not have enough free disk space to complete the cluster join operation. Depending on what browser you use - you may also just get pushed back to the clustering page and not see an error message at all.
2 or more PGP Universal Servers in a cluster environment
PGP Universal Server requires approximately 4 times the amount of disk space in use for the database on the disk available as free space on the root partition of the drive. However, it is also possible to receive this error occasionally when free disk space is not an issue but another problem occurs which returns error code 4. These other possible reasons for receiving the error message or not being able to join the cluster in general can be resolved by following our clustering requirements found in related articles section under TECH157115 - Environmental Requirements for PGP Universal Clusters.
You can check free disk space with terminal access to the PGP Universal Server with the following commands:
Command to check for free space on the root partition
If you are using a multi-partition installation then you will want to look specifically at /var location
To see how much storage space is in use on the disk for the database currently
PGP Universal Server version 3.2 and newer:
PGP Universal Server > version 3.2
Note: It needs to be approximately 4 times the size of the current disk space in use (under the corresponding pgsql data directory above).
Follow the steps in http://www.symantec.com/docs/TECH149897 to increase disk space for the Symantec Encryption Management Server. This involves doing a backup of the server to a remote location and then increasing disk space and then reinstalling and restoring from a backup.
Article URL http://www.symantec.com/docs/TECH195352