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

0002064: It is not possible to add a QOS device / 500 Internal error - due to a DataSource issue - MantisBT
MantisBT - Endian Firewall
View Issue Details
0002064Endian FirewallOther Servicespublic2009-08-05 16:012010-11-22 12:06
0002064: It is not possible to add a QOS device / 500 Internal error - due to a DataSource issue
Seems like a problem with FormEncode's locale files...

/var/log/emi reports this:
Could not load language settings: [Errno 2] No translation file found for domain: 'FormEncode'
has duplicate 0002387closed  After creating QoS devices and going back to the link I get a 500 error 
related to 0002036assigned peter-endian RBL file lets datasourcecrash 
related to 0002034assigned peter-endian datasource does not read default settings when there are no user settings 
Issue History
2009-08-05 16:01christian-endianNew Issue
2009-08-26 21:35christian-endianProjectDelemont OneShield => not released
2009-08-26 21:39christian-endianNote Added: 0002915
2009-09-03 13:51peter-endianNote Added: 0002934
2009-09-06 08:45christian-endianNote Added: 0002936
2009-09-06 08:45christian-endianAssigned To => peter-endian
2009-09-06 08:45christian-endianReproducibilityhave not tried => always
2009-09-06 08:45christian-endianStatusnew => assigned
2009-09-06 08:45christian-endianSummaryIt is not possible to add a QOS device / 500 Internal error => It is not possible to add a QOS device / 500 Internal error - due to a DataSource issue
2009-09-07 16:59peter-endianNote Added: 0002937
2009-09-07 16:59peter-endianStatusassigned => acknowledged
2009-09-07 17:00peter-endianRelationship addedrelated to 0002036
2009-09-07 17:01peter-endianRelationship addedrelated to 0002034
2009-10-27 14:10peter-endianProjectnot released => Endian Firewall
2009-10-27 14:11peter-endianTarget Version => 2.3.1
2009-11-06 12:12peter-endianRelationship addedhas duplicate 0002387
2009-11-25 16:57peter-endianProduct Versionenterprise-2.3-beta2 =>
2009-11-25 16:57peter-endianTarget Version2.3.1 => future
2010-02-17 14:10luca-endianTag Attached: purple
2010-02-23 15:11christian-endianNote Added: 0003840
2010-02-23 15:12christian-endianAssigned Topeter-endian => simon-endian
2010-02-23 15:12christian-endianStatusacknowledged => assigned
2010-02-23 15:12christian-endianTarget Versionfuture => 2.3.1
2010-02-23 15:12christian-endianNote Edited: 0003840
2010-02-26 14:16simon-endianNote Added: 0003873
2010-02-26 14:16simon-endianStatusassigned => resolved
2010-02-26 14:16simon-endianFixed in Version => 2.3.1
2010-02-26 14:16simon-endianResolutionopen => fixed
2010-11-22 12:06peter-endianStatusresolved => closed

2009-08-26 21:39   
FormEncode does indeed not provide an English translation. However, that is not a problem since the exception is caught and the string itself is returned.

Something else must be the real problem.
2009-09-03 13:51   
works also for me. maybe this happens only due to a strange problem on your machine?
2009-09-06 08:45   
Original title was: It is not possible to add a QOS device / 500 Internal error

The problem arises when an OpenVPN client connection (or an uplink - have not tried that, but should be the same problem) is created with capital letters in its name because each connection is stored in a directory with that name.

In the getVPNs function uses the DataSource to read the configuration which in turn accesses every key by using lower(). As for now we do not map filenames though.

Possible solutions:
1. Fix DataSource
2. Make sure these directories are always created lowercase (Would require a migration script as well as fixes in efw-network and efw-vpnclient).
2009-09-07 16:59   
solution 1 is the better one - we know that, don't we? :)
2010-02-23 15:11   
(edited on: 2010-02-23 15:12)
We'll have to go with solution 2 for now:

Keep in mind that affected VPN connections must be closed before migrating and then restarted!

Make sure to not only rename the directory but change the name in the settings file as well.

2010-02-26 14:16   
implemented solution2 -> folder and name key are renamed and condstop before / start after is triggered for the effected vpnclient connections

from now on name of new profiles will be lowercased