Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Policy Enforcer Log File Locations

 

The following Policy Enforcer configuration settings files are located under /srv/feeder/etc/log:

Note

Do not edit these files unless instructed by the Juniper Networks Technical Assistance Center (JTAC).

  • auto_upgrades_log.yml—Internal use only.

  • config_server_log.yml—Defines the format for the config_server.log file. For example, message and date format and maximum file size.

  • feeder_cleaner_log.yml—Internal use only.

  • feed_scheduler_log.yml—Defines the format for the feed_scheduler.log file. For example, message and date format and maximum file size.

  • feed_server_log.yml— Defines the format for the feed_server.log file. For example, message and date format and maximum file size.

  • ha_vip_controller_log.yml—Internal use only.

  • upgrades_cli_log.yml—Internal use only.

The following Policy Enforcer log files are located under /srv/feeder/log. By default, a maximum of 10 files are created for each log file. For example, config_server.log, config_server.log.1, config_server.log.2, etc. After 10 files are created, the oldest file (in this example, config_server.log) is overwritten next.

  • config_server.log—Contains log messages for the interaction of Security Director with Policy Enforcer.

  • feed_scheduler.log—Contains log messages for the downloading of feeds.

  • feed_server.log—Contains log messages for distributing feeds to the SRX Series devices.

The following Policy Enforcer log files are located under /var/log:

  • prepare_vm.log—Contains information about your Policy Enforcer software installation.

  • pe_upgrade.log—Contains information about your Policy Software software upgrade.