@pkowalewski PA 5020 is a connected to panorama ? What is device state ? - Is Connected status When we deploy Panorama 7.1.x the logs works. When we deploy Panorama 8.x in legacy mode the logs works When we deploy Panorama 8.x in the new "Panorama mode" the logs not works @BPry Do your content versions match on Panorama and the 5020? My initial guess would be that they don't and that is why you are seeing these errors. You would want your Panorama to match your content releases or be a lower release than your firewalls, if your Panorama has a higher content version then you will get random issues like this when attempting to collect those logs. Content version are the same in both devices. @vsys_remo On what panorama version are you exactly? Did you do a simple reboot? Did you check the disk status? Did you try to remove and add the disks again to your local log collector? (Do not try this when you still have logs on that log collector, may be from migrating to panorama mode, but since you wrote that you deploy a new panorama...) Did you delete and add the local log collector? - Panorama 8.0.2 fresh install - The reboot did not fix the problem - Disk status: # show system disk-space Filesystem - Size - Used - Avail - Use% - Mounted on /dev/sda2 - 8.0G - 2.3G - 5.3G - 30% - / /dev/sda5 - 24G - 1.5G - 22G - 7% - /opt/pancfg /dev/sda6 - 6.0G - 1.6G - 4.2G - 28% - /opt/panrepo tmpfs - 7.9G - 110M - 7.8G - 2% - /dev/shm cgroup_root - 7.9G - 0 - 7.9G - 0% - /cgroup /dev/sda8 - 32G - 11G - 20G - 35% - /opt/panlogs /dev/sdb1 - 2.1T - 68M - 2.1T - 1% - /opt/panlogs/ld1 /dev/loop0 - 9.9G - 151M - 9.2G - 2% - /opt/logbuffer - I'm not migrating from legacy to panorama mode. I install it from scratch on 8.0.2 with all pre-requisits for Panorama Mode.
... View more