tyler.durden
/
icingaweb2-module-director
mirror of https://github.com/Icinga/icingaweb2-module-director.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc/faq: formatting, more hints

This commit is contained in:
Thomas Gelf 2016-03-25 13:25:12 +01:00
parent 634472792a
commit 3fd9a4c0de
1 changed files with 15 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
doc/80-FAQ.md
View File

@ -4,13 +4,26 @@ Frequently Asked Questions
I got an exception...
---------------------
Refusing to render the configuration, your DB layer corrupts binary data. You might be affected by Zend Framework bug #655
This section tries to summarize well known pitfalls and their solution.
### Binary data corruption with ZF 1.12.6 and 1.12.17
When deploying your first configuration, you might get this error:
Refusing to render the configuration, your DB layer corrupts
binary data. You might be affected by Zend Framework bug #655
Sad but true. Zend Framework 1.12.16 and 1.12.17 silently corrupt binary data. You can either wait for 1.12.18 or downgrade to an earlier version. Debian Stable currently ships 1.12.9, but as they backported the involved erraneous security bug their version is affected too.
You could also manually fix this issue in `/usr/share/php/Zend/Db/Adapter/Pdo/Abstract.php`. Search for the `_quote` function and delete the line saying `$value = addcslashes($value, "\000\032");`. Please note that doing so would fix all problems, but re-introduce a potential security issue affecting the MSSQL and Sqlite adapters.
SQLSTATE[HY000]: General error: 2014 Cannot execute queries while other unbuffered queries are active.
### Connection error when setting up the database
When setting up and validating a database connection for Director in Icinga Web 2, the following error might occur:
SQLSTATE[HY000]: General error: 2014 Cannot execute queries while
other unbuffered queries are active.
This happens with some PHP versions, we have not been able to figure out which ones and why. However, we found a workaround and and fixed this in Icinga Web 2. Please pull from the current Icinga Web 2 master or at least apply this fix to your installation: