Log percentage and space

[jdprovine]

If logging is set to allow up to 95% space on the disk and it hits 95% that same partition,/dev/md6 3.8G 3.2G 454M 88% /opt/panrepo      - PAN-OS Image repository.(Device/Software), resides the PAN OS what happens when you hit 95% on logs and try to install a new OS

[jdprovine]

@reaper @BPry @Mick_Ball @OtakarKlier

When i don't get answers I explicitly add you guys 🙂

[reaper]

The price of fame! 😉

Ehm

/ is where the OS is installed (contains some system (operating system native) logs)
/opt/panrepo is where content updates and images etc are downloaded and stored
/opt/panlogs is where the log database is stored (all firewall logs)

The 95% you refer to is the /opt/panlogs partition, so it does notningluence OS installs

[BPry]

@jdprovine,

In addition to what @reaper stated, having the logs at 95% assigned capacity really doesn't matter. Potentially, during an update where the firewall has to convert the logs it would simply take a longer time to complete the convertion process, simply because there are more logs present. 

[jdprovine]

@reaper

Is this a European word " notningluence" I am not familiar with it LOL,

Yeah we have talked about this more than once and I have this information based on those discussion

/dev/md6 3.8G 3.2G 454M 88% /opt/panrepo - PAN-OS Image repository.(Device/Software)

/dev/md2 3.8G 3.0G 594M 84% / - OperatingSystem and it's logs ('daemon' logs)

/dev/md8 198G 113G 75G 61% /opt/panlogs - Allocated for PAN logs. (firewall LogDatabase)

/dev/md5 7.6G 3.3G 4.0G 46% /opt/pancfg - Pan-OS configuration.

cgroup_root 2.0G 0 2.0G 0% /cgroup

The logs setting I am referring to that are set to 95% are found under the device tab\management tab\logging and reporting settings

[jdprovine]

@BPry

Good to know. Support just told me if I run into any issues just clean up the logs and they couldn't explain anything to me

[reaper]

"Does not influence"
Was fat-fingering my phone keyboard 😉

You won't run into issues with the /opt/panlogs as this is essentially a single database that has it's own cleanup algorithms (old logs out, new logs in)
On a fresh install the partition will be 'quite' empty and then steadily fill up until 95% at which point it will start kicking out old logs in favor of new ones

Anything you configure on the web interface will only influence /opt/panlogs