The GaussDB database generates a large volume of run logs during operation. You are advised to retain run logs generated in the latest one month only and clear other logs to prevent disk space waste.
Prerequisites
- A cross-platform remote access tool, such as PuTTY, has been obtained.
- The management IP address of the management server where the eReplication Server resides has been obtained.
- The login password of user root or DRManager in Linux.
Context
- The names of logs generated by the GaussDB processes start with gaussdb. In Linux, these logs are saved to /opt/gs/app/data/pg_log.
- The log files are named in the format of gaussdb-Year-Month-Day_HHMMSS.log.
Procedure
- In Linux, clear GaussDB run logs.
- Use PuTTY to log in to the eReplication management server.
In software package-based installation mode: Log in as user root.
- Run the TMOUT=0 command to prevent PuTTY from exiting due to session timeout.
After you run this command, the system continues to run when no operation is performed, resulting a risk. For security purposes, you are advised to run exit to exit the system after completing your operations.
- Clear logs.
- Run the cd /opt/gs/app/data/pg_log command to go to the directory where the logs reside.
- Back up logs that are generated more than one month ago.
- Run the rm log name command to delete logs.
- Use PuTTY to log in to the eReplication management server.