session end reason resources-unavailable for all traffic

[miaocongcong]

Hi,Guys

The customer's network recently experienced an outage, and  found all the session  end reason  was resources-unavailable ;

I exec the comand " debug dataplane pool statistics" and found there is a parameter in the software pool called Regex Results that has been exhausted. Compared with normal firewalls, this value should not be reduced. I also tried to execute “set deviceconfig setting session resource-limit-behavior bypass” , but this solution is not acceptable to customers.
At present, the customer's system version is 9.1.13 of the PA3000 series, which has been rolled back to 9.1.12, and the parameters are normal
Does anyone know if this is a bug?

Customer needs an official explanation，thanks in advance！

[IljaCigna]

on 9.1.14-h4 it is still happening (VM 300) and started when we were on 9.1.3 with the key difference being that the counter mentioned in either version has not been increasing, remained at 0 at all times including during sessions being dropped. In our case this happens at very specific times of the day (around 8 AM and 8 PM every day). It is for very specific traffic between two hosts which however for the rest of the day has no issues. Something clearly triggers this within PAN OS and it goes away when that specific traffic is no longer passing through. We could recreate the issue at will. It happens to sessions of any total size, just a few kilobytes as well as tens of megabytes long. We have logged this with TAC a couple of days ago.

[AaronAxvig]

I am still seeing this on 9.1.14-h4 as well.  FTP transfer of 4.5MB file jams up after 2.5MB with resources-unavailable logged.

[RomainSalmon]

Hello,

We had this issue for our 5250 despite of the upgrade. After opening a TAC case, the session ends with a resources-unavailable reason as the ctd-pkt-proc-loop counter is being triggered : (show session info)
tracker stage l7proc : ctd pkt loop
end-reason : resources-unavailable

Cause of the issue:- During the packet processing, ctd reaches the max number of loops which triggers the ctd_pkt_proc_loop counter and ends the session with resources-unavailable.

Resolution:- Increasing the number of loops would allow ctd to finish processing the packet buffers so the session will not end due to reaching the max number of loops.

- Please change the number of allowed loops to 8190 using the following commands.
set system setting ctd pkt-proc-loop-low 8190
set system setting ctd pkt-proc-loop-high 8190

- After changing loop values revert resource limit behavior to drop followed by a commit.
>configure
# set deviceconfig setting session resource-limit-behavior drop
# commit
- After commit is complete, verify new loop values using the following command.
>show system setting ctd state | match loop

I hope that gonna help some people !