Bug #15914
open
PHP error when a queue is added with the same name as a limiter
Added by Richard Ball 14 days ago.
Updated about 8 hours ago.
Category:
Traffic Shaper (Limiters)
Plus Target Version:
25.03
Affected Architecture:
All
Description
[07-Dec-2024 17:03:55 US/Pacific] PHP Fatal error: Uncaught Error: Call to a member function addGlobal() on null in /usr/local/www/firewall_shaper_vinterface.php:387
Stack trace:
#0 {main}
thrown in /usr/local/www/firewall_shaper_vinterface.php on line 387
Files
Issue appears when creating a queue for a second limiter.
I'm not able to induce this on 24.11. I can add and remove queues and limiters as much as I'd expect.
Does this happen consistently each time you try to add the queue? Does it happen with multiple limiters or just a single one? Any more info you can give so we can reproduce this would be helpful.
I was able to recreate this on accident, it seems naming the child queue the same as the parent limiter sets off one of the 50x errors. I hit this when I was trying to backspace quickly and hit enter after backspacing too many times on the queue name.
I think you nailed it Jordan.
I was able to create the queue when it wasn't named the same as the limiter. Once it's the same name, the error 50 appears.
- Status changed from New to Confirmed
- Affected Architecture All added
- Affected Architecture deleted (
SG-1100)
- Project changed from pfSense Plus to pfSense
- Subject changed from PHP Fatal error when creating queue for limiter to PHP error when a queue is added with the same name as a limiter
- Category changed from Traffic Shaper (Limiters) to Traffic Shaper (Limiters)
- Status changed from Confirmed to In Progress
- Assignee set to Marcos M
- Target version set to 2.8.0
- Affected Plus Version deleted (
24.11)
- Plus Target Version set to 25.03
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by