/var/log/asterisk/full filling up with lines about queue, HD full now

I don’t know what could have caused this so I’m hoping someone here has an idea. Obviously the log shouldn’t be allowed to go to 19 GB but it looks like a different underlying issue. I see 30,000 lines of

[2015-01-15 03:36:25] VERBOSE[1342][C-00023353] pbx.c: – Executing [[email protected]:1] Set(“Local/[email protected];2”, “QAGENT=7000”) in new stack
[2015-01-15 03:36:25] VERBOSE[1342][C-00023353] pbx.c: – Executing [[email protected]:2] Goto(“Local/[email protected];2”, “7000,1”) in new stack
[2015-01-15 03:36:25] VERBOSE[1342][C-00023353] pbx.c: – Goto (from-queue,7000,1)
[2015-01-15 03:36:25] VERBOSE[1342][C-00023353] pbx.c: – Executing [[email protected]:1] Set(“Local/[email protected];2”, “QAGENT=7000”) in new stack
[2015-01-15 03:36:25] VERBOSE[1342][C-00023353] pbx.c: – Executing [[email protected]:2] Goto(“Local/[email protected];2”, “7000,1”) in new stack

All at 3:30 AM no less.

This is a virtual machine running 5.211.65-20 (FreePBX 2.11.0.39 )

You need to set up log rotation for your 19GB files and secure your machine with a firewall/fail2ban/whaetver, with 30000 of those then you are being actively attacked, they like to do that in the middle of the night and on Sundays, I could never figure out why :wink: .

Is queue 7000 defined? What it looks like to me is that it’s hitting the fallback extension (_.) when it tries to execute [email protected], and NODEST happens to also be set to 7000. You could check the log to find where NODEST gets set on that channel.