Autocommit failures post abrupt reboot and logrcvr crashes
324
Created On 07/01/26 00:22 AM - Last Modified 10/04/26 22:09 PM
Symptom
- Error "System is not ready. Please try later. " is received when running any of the show commands like show interface all
- Show jobs all indicates tha tthe Autocom job has failed
Environment
- Palo Alto Firewalls : PA-220, PA-850, PA-440
Cause
- Logrcvr daemon is in stopped process since it is crashing repeatedly causing the Autocommit to fail. Since the autocommit doesnt complete, the device's dataplane does not initialise causing the device to not process any traffic.
- The logrcvr daemon is crashing because of the abrupt shutdown of the device causing the hipmatch logs in the device to get corrupted.
Resolution
- Confirm with show jobs all, if the autocommit process has failed.
- Check the status of the logrcvr daemon in the device with "show system software status | match logrcvr" , It will be seen in stopped state.
- Check for the presence of the crash files for logrcvr process with the command show system files. The logrcvr process is seen to be crashing every minute.
- Since the process is crashing repeatedly, the next step is to check the crashinfo file to see the threads in the crash file.
- For this, generate a tech support file of the device and open up the TSF and navigate to the ./var/cores/crashinfo path and then open up any of the crash files via a notepad editor.
- Once any of the crashinfo files is open, check if the thread with the name "pan_logrec_get_flatbuf_hipmatch_receive_time" is present in the file alongwith the below threads:
"is_query_done"
"pan_logdb_cursor_next_with_storage_type" - If these are present, we will need clear up the hipmatch logs in the device with the command: clear log hipmatch.
- Once the logs are cleared, proceed to restart the logrcvr process with the command : debug software restart process log-receiver
- Verify if the solution has worked with another commit via the device's CLI as below:
configure
commit force
exit - If it still fails, raise a support TAC case alongwith the putty cli logs where the above steps where performed and the new tech support file of the firewall.