04-19-2012 04:46 AM
Greetings Again,
Off late I have been hit with quite a few surprises after the release of version 4.1.x. Now this is the latest one that surprises me.
Over the last few months one of my customer's PA-2050 has randomly rebooted which obviously has a large impact on our users ( I was never told of these till today). The customer is presently running version 4.1.0.
Today it rebooted around 10:30 after a security policy was added to the rule base and a commit was submitted (rule was to allow a specific host machine to access a specific IP address). For info. since the reboot this new rule is no longer in the rule base. After looking through the system log, I found the following error 'infra-group: restarts exhausted, rebooting system'.
As far as I understand, there were similiar or same issues in version 3.1.x which was fixed in version 3.1.7 upstream. Can someone let me know what is the cause behind?
Thanks in Advance.
Kalyan
04-20-2012 06:29 AM
Looks like the log-indexer was being triggered for indexing regular traffic and threat logs. Due to the log file size and number of fields being indexed simultaneously, the log-indexer might use more than 500 Mb memory, that pushes other daemons into swap, causing system become non-responsive or cause daemon killed due to lose of heartbeat resulting in restarts.
This bug had re-occured in version 4.1.1 and was fixed in 4.1.4.
Cheers..
Kal
04-19-2012 06:29 AM
Hi...You can check the release notes for 4.1.1 and so on to see the bug fixes. I do recommend that you upgrade to PAN-OS 4.1.5. Thanks.
04-19-2012 06:33 AM
First, it was a bug and was fixed. Has it re-occured again??
Second, is it a bug? If it is not a bug then there is no point in going through the release notes (by the way I did go through the release notes before posting this topic).
Third, yes, I will be upgrading the customer to version 4.1.5
But, again this does not answer my question. I am more curious in finding what does it mean and what is the cause behind it. Answer to this question will really help me.
Thank you
Regards,
Kal
04-20-2012 06:29 AM
Looks like the log-indexer was being triggered for indexing regular traffic and threat logs. Due to the log file size and number of fields being indexed simultaneously, the log-indexer might use more than 500 Mb memory, that pushes other daemons into swap, causing system become non-responsive or cause daemon killed due to lose of heartbeat resulting in restarts.
This bug had re-occured in version 4.1.1 and was fixed in 4.1.4.
Cheers..
Kal
10-25-2012 08:17 AM
Hi,
I would like to get an answer for error "ERROR: infra-group: restarts exhausted"
Thanks.
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!
