This article explains what must be does when the Policy Enforcer disk fills up with logs over time.

Policy Enforcer is out of disk space.

Policy Enforcer processes have debug logging enabled by default, and it is best to leave debug on for future troubleshooting:

Path: /srv/feeder/log/

The best and easiest way to delete old log data is to delete from /srv/feeder/log/ .

However, do not delete files without dates in the filename when Policy Enforcer is running. Instead, use a command such as the following:

To remove all files from 2019 (excluding the active files without year in the name):

rm -f  /srv/feeder/log/*2019*

(Make sure that there are NO spaces before the " * " characters. If there are spaces, it will delete MORE than you want.)

Policy Enforcer versions prior to Junos OS Release 19.1 may use a large amount of disk space in /var/lib/feeder/feed_data over time. Do NOT delete anything from this directory. These are required for feeds to function correctly. Junos OS Release 19.1 includes cleanup code to reduce the disk space used here. It is recommended to upgrade to Junos OS Release 19.1.

Note that the best option is to upgrade your PE to the latest Junos OS Release 21.2 , which has a new feature to purge feeds that are older than a specified number of days.

2021-12-10: Added new purge feature details from PE-21.2 release