SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0002706: restartqos --debug returns errors - MantisBT
MantisBT - Endian Firewall
View Issue Details
0002706Endian FirewallFirewall (iptables)public2010-02-22 10:092010-11-22 12:08
aender 
peter-endian 
highmajoralways
closedfixed 
2.3 
2.3.12.4.1 
0002706: restartqos --debug returns errors
Look at this output form restartqos --debug

I post only the lines with errors:

2010-02-22 11:02:23,090 - restartqos.py[14635] - ERROR - Migration has to be fixed!!!
2010-02-22 11:02:23,308 - restartqos.py[14635] - DEBUG - STDERR [tc filter add dev br0 parent ffff: protocol ip prio 50
                  u32 match ip src 0.0.0.0/0 police rate 3932kbit
                  burst 10k drop flowid :1]
RTNETLINK answers: Invalid argument
We have an error talking to the kernel
/bin/sh: line 1: u32: command not found
/bin/sh: line 2: burst: command not found
2010-02-22 11:02:23,661 - restartqos.py[14635] - DEBUG - STDERR [tc filter add dev eth1 parent ffff: protocol ip prio 50
                  u32 match ip src 0.0.0.0/0 police rate 3932kbit
                  burst 10k drop flowid :1]
RTNETLINK answers: Invalid argument
We have an error talking to the kernel
/bin/sh: line 1: u32: command not found
/bin/sh: line 2: burst: command not found


I think the u32 and burst are the biggest problem that causes the most bugs in conjunction with QoS bugs. Both are no binarys. u32 and burst are options of the tc binary.
So i think there are any values wrong in the database or some typos at the scripts for QoS.

I tried to look for the scripts and configs of QoS but i doesn´t found all.
I saw that the most things are done with emi and sqlite.

Can you explain me the whole config and scripts for more troubleshooting?

No tags attached.
Issue History
2010-02-22 10:09aenderNew Issue
2010-02-22 10:13aenderNote Added: 0003823
2010-02-22 11:08peter-endianStatusnew => confirmed
2010-02-22 11:08peter-endianTarget Version => 2.3.1
2010-02-23 10:02aenderNote Added: 0003838
2010-03-03 15:19ra-endianAssigned To => peter-endian
2010-03-03 15:19ra-endianStatusconfirmed => assigned
2010-03-03 15:49ra-endianPrioritynormal => high
2010-03-08 10:52peter-endianStatusassigned => resolved
2010-03-08 10:52peter-endianFixed in Version => 2.3.1
2010-03-08 10:52peter-endianResolutionopen => fixed
2010-11-22 12:08peter-endianFixed in Version2.3.1 => 2.4.1
2010-11-22 12:08peter-endianStatusresolved => closed

Notes
(0003823)
aender   
2010-02-22 10:13   
some more errors at the output

2010-02-22 11:02:23,111 - restartqos.py[14635] - ERROR - RETURNCODE [iptables -t mangle -N QOS 2> /dev/null] 1
2010-02-22 11:02:23,192 - restartqos.py[14635] - ERROR - RETURNCODE [iptables -t mangle -N QOS_BR0 2> /dev/null] 1
2010-02-22 11:02:23,223 - restartqos.py[14635] - ERROR - RETURNCODE [iptables -t mangle -D QOS -o br0 -j QOS_BR0 2> /dev/null] 1
2010-02-22 11:02:23,539 - restartqos.py[14635] - ERROR - RETURNCODE [iptables -t mangle -N QOS_ETH1 2> /dev/null] 1
2010-02-22 11:02:23,572 - restartqos.py[14635] - ERROR - RETURNCODE [iptables -t mangle -D QOS -o eth1 -j QOS_ETH1 2> /dev/null] 1
(0003838)
aender   
2010-02-23 10:02   
Any updates about all the QoS Bugs?