Queue loop, 100% CPU usage

General Help
1

I was troubleshooting a problem today, where a customer is noticing that once in a while, callers are hung up on while parked. I had the user park me, and after the call rolled back, park me again, hoping to get hung up on…I never got hung up on, but I did crash the PBX. After about 3 parks, I got the following looping in the console. Had to amportal restart to get it to stop:

-- Executing [[email protected]:2] Goto("Local/[email protected];2", "4153,1") in new stack -- Goto (from-queue,4153,1) -- Executing [[email protected]:1] Set("Local/[email protected];2", "QAGENT=4153") in new stack

Has anyone else seen this? 4153 is the extension that was parking me. I am running FreePBX 2.9, on a 64bit system. The dialplan is pretty straightforward, with just a few queues, but ~350-400 users at any given time.

Thanks!

edit_______

This is probably more helpful, sorry:

-- Stopped music on hold on Local/[email protected];2 [Jan 31 16:03:11] NOTICE[4057]: features.c:4174 manage_parkinglot: Dial features not found on Local/[email protected];2, using default! -- Added extension '[email protected]' priority 1 to park-dial == Timeout for Local/[email protected];2 parked on 2101 (default). Returning to parkedcallstimeout,[email protected],1 -- Executing [[email protected]@parkedcallstimeout:1] ExecIf("Local/[email protected];2", "1?Set(CALLERID(name)=PARK:CONTEXTWB)") in new stack -- Executing [[email protected]@parkedcallstimeout:2] Goto("Local/[email protected];2", "park-dial,[email protected],1") in new stack -- Goto (park-dial,[email protected],1) -- Executing [[email protected]@park-dial:1] Dial("Local/[email protected];2", "Local/[email protected],30,t") in new stack -- Called Local/[email protected] -- Executing [[email protected]:1] Set("Local/[email protected];2", "QAGENT=4153") in new stack -- Executing [[email protected]:2] Goto("Local/[email protected];2", "4153,1") in new stack -- Goto (from-queue,4153,1) -- Executing [[email protected]:1] Set("Local/[email protected];2", "QAGENT=4153") in new stack

That is where it started. Thanks again.

2