The large log files continuously generated by the PSMP component are taking up disk space

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

The large log files continuously generated by the PSMP component are taking up disk space

L0 Member

Why does the PAM log system continue writing repetitive logs as shown below, causing our PSMP server disk to become full? Is this a configuration bug or the system’s default behavior?

 

please help

Field_Content_versions_oct20__068Vy00001KsjybIAB.png

1 accepted solution

Accepted Solutions

L5 Sessionator

Hey @Rahman Ramadan​ Building on what others have mentioned, if a user is performing diagnostics with a lot of data written to the console (such as a long running scripts, etc.) this will generate a lot of audit data because of Trace messages for every line of output.

 

I recommend Connection Client Settings TraceLevels=0 when not troubleshooting an active issue. Alternatively, you can instruct users to write the data to a file, versus to the console if you intend on leaving debugging on 24/7.

 

Additional Resources:

https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/configuring-debug-levels.htm

View solution in original post

4 REPLIES 4

L7 Applicator

“The PSMP server filled its disk due to continuous SSH and session logging, which is standard PSMP behavior. Log growth was accelerated by elevated logging levels / missing rotation. This is not a product defect but a configuration and capacity management issue. CyberArk recommends log rotation (built-in from v13.2) and controlled debug levels to prevent recurrence.”

L4 Transporter

Hi,

also you can check if your users are using commands like "screen" or "watch", they create huge logs in the PSMP.

Regards,

 

L5 Sessionator

Hey @Rahman Ramadan​ Building on what others have mentioned, if a user is performing diagnostics with a lot of data written to the console (such as a long running scripts, etc.) this will generate a lot of audit data because of Trace messages for every line of output.

 

I recommend Connection Client Settings TraceLevels=0 when not troubleshooting an active issue. Alternatively, you can instruct users to write the data to a file, versus to the console if you intend on leaving debugging on 24/7.

 

Additional Resources:

https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/configuring-debug-levels.htm

L4 Transporter

Hi @Rahman Ramadan​ 

Several community members have shared answers to your question. Could you let us know if any of these resolved your issue?

If so, please mark the appropriate answer as “Select as Best” to help other members find the solution easily.

If the issue remains unresolved, I recommend submitting a ticket with our support team for further assistance.

Thank you,

Shaked

  • 1 accepted solution
  • 105 Views
  • 4 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!