Search Our Database

How to empty DirectAdmin system messages for admin and user levels

Last updated on |
by

Introduction

DirectAdmin stores system messages at both the Admin and User levels. These messages accumulate over time and can take up disk space unnecessarily. This guide will walk you through clearing the system messages for both the Admin and User levels.

 

Prerequisites

  • SSH access to the server
  • Admin-level privileges on the DirectAdmin server
  • Basic knowledge of the command-line interface to navigate and execute commands

 

Step-by-Step Guide

Empty admin level system messages

Admin-level system messages are stored separately and need to be cleared manually through the command line.

1. Access your servia via SSH using a terminal or SSH client such as PUTTY.

 

2. Once logged in, navigate to the admin message storage directory by running tjhe following command:

cd /usr/local/DirectAdmin/data/admin

 

3. Clear the admin system message list by running the following command:

echo -n "" > tickets.list

This command will empty the tickets.list file, effectively clearing all admin-level system messages.

 

Empty user level system messages

To clear system messages for a specific user, you’ll need to repeat the process for each user account individually.

1. Navigate to the user’s message storage directory. Replace username with the actual username for the account you want to clear:

cd /usr/local/DirectAdmin/data/users/username

 

2. Run the following command to empty the user system message list:

echo -n "" > tickets.list

This will clear the messages for that particular user. Repeat this process for any additional users if needed.

 

Conclusion

By following the steps outlined above, you can efficiently manage and delete both Admin and User level messages. Always ensure that no important messages are lost in the process, and repeat the steps periodically to prevent the buildup of unnecessary data. For additional assistance or if you encounter any issues, please contact our support team at support@ipserverone.com.

 

 

Article posted on 20 April 2020.