Why is PCoIP Management Console 2.4.0 out of disk space?
Answer:
We have experienced an issue where PCoIP Management Console 2.4.0 is out of disk space and have tracked it to the hosts file being set incorrectly.
When the host file is incorrectly set, it prevents the auto vacuum process is not running. This causes the table log_message file to grow.
DO NOT USE DNS CONFIG TOOL
To diagnose issue:
Do a database backup if space permits and download
Change to the root directory cd /
Run the following command to find out which volume is using the space - df --total
Run the following command to determine which directory is using the space - sudo du -s * | sort -n
Run the following command to determine which file is using the space - sudo du -h |sort -n -r |more
If you want to save the output to a file then use this command - sudo du -h |sort -n -r |more>/home/admin/paul
If you still have space:
Fix hosts file - sudo nano /etc/hosts
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
Restart the network service - sudo service network restart
Wait overnight for the vacuum service to run, it needs to log in as localhost.
If you are out of space:
Log into psql - psql pcoip_mc_db postgres
View log_message size - select count(1) from log_message; (if huge this is issue)
You will need to delete the log_message table - delete from log_message;
You will need to run vacuum command - vacuum full log_message;
To quite the database \quit
We believe if it is related to the hosts file by fixing the hosts file the autovacuum will run when next scheduled.
Pertains to:
- PCoIP Management Console 2.4.0