I would like to know why Daemons and processes ids are getting suspended or not working.
I can see that which daemon stopped working by this cmd,
> show system software status
and for example: routed is stopped and i have restarted the routed process.
But here i want to know what caused that daemon to not work ?
Is there a way to check why daemon going suspended ?
If it can be found in TSF using Auto assistance or PANTS tool, please do let me know.
Note: routed is just an example, i want to know generally for all daemons...!
each daemon/process has a log in mp-log or dp-log and most can be set to enhanced debug logging, but before you dive deep into this, which PAN-OS version are you running and which platform?
if you're on an older PAN-OS, try upgrading as you're most likely running into a bug
else try enabling debugging on processes you see in this state regularly:
> debug routing global on debug
and after routed goes into the state again
> less mp-log routed.log
Thanks for your reply.
Customer runs 9.0.7.
I have a query that what if customer restarts the daemon or pid and then generates the TSF and share it to find the RCA. ? becuz there will not be a debugging and we cannot deep dive into logs..! In such cases will it be able to find why daemon or PID stopped working ??
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!