As the title says, Panorama receives logs just fine but will not show them in the GUI.
I noticed this today. Disks shows unavailable in panorama but in the CLI they're fine.
I'm actually pretty convinced this is related to the elastic search process.
After a graceful shutdown/power up of the Panorama VM I noticed the following:
show system software status ... Process elasticsearch restarting (pid: -1) - Exit Code: 1 ...
Every time you run this command, this process comes back with a new PID (which leads me to believe it's constantly restarting). Each of these are within 10-15 seconds of each other:
show system software status ... Process elasticsearch running (pid: 27029) ...
show system software status ... Process elasticsearch running (pid: 27157) ...
show system software status ... Process elasticsearch running (pid: 27658) ...
show system software status ... Process elasticsearch running (pid: 27399) ...
I've restarted this management server probably 10 times. The only thing it seems to do is restart services freeing up the CPU long enough to seem stable, but then it ramps back up. Still no logs either.
None of which seem to help. My hunch is the elasticsearch service is bugged out, eventually causing the CPU to spike, eventually causing the whole system to become unstable. Nothing seems to bring logs back to the UX either.
Gonna keep going here...I noticed that the "java" process is exceptionally high (90% - 420%). Turns out, JAVA is used to do reporting & logging/indices. Funny enough, those are the exact things I cannot get Panorama to do. Panorama - JAVA Process
To further my hunch about elasticsearch - it is 100% restarting constantly. Running "show system software status | match elasticsearch" back-to-back 10 times in a row confirms it, I saw at least once where the service was "restarting (pid: -1) - Exit Code: 1".
Since elasticsearch is written in JAVA, I can only assume that fixing this service will fix a lot of my other issues.
There have been a few issues with the elasticsearch indices causing exactly the problem you're having. (PAN-114041 is one example)
Make sure you're on at least PAN-OS 8.1.7 (it could have happened on a later version too, I didn't see it skimming through though) and you will need to contact support to help you clear those indices as root access is required.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The Live Community thanks you for your participation!