Bug #15914
closed
PHP error when a queue is added with the same name as a limiter
100%
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
Updated by Chris W about 1 month ago
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.
Updated by Jordan G about 1 month ago
- File PHP_errors.log PHP_errors.log added
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.
Updated by Richard Ball about 1 month ago
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.
Updated by Jordan G about 1 month ago
- Affected Architecture All added
- Affected Architecture deleted (
SG-1100)
Updated by Marcos M 29 days ago
- 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
Updated by Marcos M 29 days ago
- Status changed from In Progress to Feedback
- % Done changed from 0 to 100
Fixed with 2b324392cddc24906f1d4dc203089de8d6065439.
Updated by Kris Phillips 23 days ago
- Status changed from Feedback to Resolved
Jordan G wrote in #note-9:
with patch applied, attempting to create a child queue with the same (name) as the parent produces an error stating they cannot have the same name
Confirmed. I see the same thing now on 25.03. Marking Resolved.