[ZBX-7727] Frontend does not receive error message when connection to DB is failed Created: 2014 Jan 30  Updated: 2017 May 30  Resolved: 2014 Feb 11

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 2.0.11rc1, 2.2.2rc1
Fix Version/s: 2.2.3rc1, 2.3.0

Type: Incident report Priority: Major
Reporter: Alexey Pustovalov Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: database, errorstatus
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

PostgreSQL, Oracle, DB2, SQLite


Attachments: PNG File wordbreak.png    

 Description   

Frontend shows message 'Error connecting to database' when connection to DB is failed. There must be error message from DB as well.



 Comments   
Comment by Oleg Egorov (Inactive) [ 2014 Feb 07 ]

FIXED IN svn://svn.zabbix.com/branches/dev/ZBX-7727 r42350

Comment by Pavels Jelisejevs (Inactive) [ 2014 Feb 07 ]

There's no way to get a connection for PosgreSQL, so it won't be displayed for this database.

Comment by Pavels Jelisejevs (Inactive) [ 2014 Feb 07 ]

(1) No error message displayed for SQLite.

oleg.egorov Won't be fix, Zabbix now don't support SQLite, CLOSED

Comment by Pavels Jelisejevs (Inactive) [ 2014 Feb 07 ]

(2) It would be better to remove the brackets around the error message and add a dot in the end. Also, please add a dot for PosgreSQL message. And a colon is missing in the MySQL message.

oleg.egorov RESOLVED IN r42423, r42424, r42452

jelisejev Please also add a dot in the end of the error messages.

oleg.egorov RESOLVED IN r42490

jelisejev We decided not to a dot in the end, since some database error messages already contain a dot. CLOSED.

Comment by Pavels Jelisejevs (Inactive) [ 2014 Feb 07 ]

(3) In the setup in an error message is too long, it shouldn't break words.

oleg.egorov RESOLVED IN r42423, r42424

jelisejev The line is too long.

oleg.egorov RESOLVED IN r42490

jelisejev CLOSED.

Comment by Pavels Jelisejevs (Inactive) [ 2014 Feb 07 ]

(4) Instead of passing an already formatted message to general.warning.php, I suggest to pass the header and message separately and move formatting to the view.

Also, please remove the colon after "Configuration file error" in setup.php:28 and config.inc.php:36.

oleg.egorov RESOLVED IN r42423, r42424

jelisejev
1. There shouldn't be a colon after "Database error".
2. The parameters should be passed as inline arrays, without using the $message variable.

oleg.egorov RESOLVED IN r42490

jelisejev Please review my change in r42606.

Comment by Pavels Jelisejevs (Inactive) [ 2014 Feb 13 ]

TESTED.

Please review (4) before merging.

oleg.egorov CLOSED

Comment by Oleg Egorov (Inactive) [ 2014 Feb 17 ]

FIXED IN 2.2.3rc1 r42719, 2.3.0(trunk) r42720

CLOSED

Generated at Sun Jun 15 13:56:51 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.