Details
-
Type:
Bug
-
Status: To Do
-
Resolution: Unresolved
-
Fix Version/s: None
-
Component/s: Qserv
-
Labels:None
-
Team:Data Access and Database
Description
Missing qservCssData db crashes Qserv when issues a sql query through czar:
The error message should be more clear and written to qserv-czar.log instead of console (console log should be thrown away in production).
as of May 2019 the mysqlproxy behavior is as follows
MariaDB [(none)]> use qservTest_case01_qserv;
|
Database changed
|
MariaDB [qservTest_case01_qserv]> select objectId from Object;
|
ERROR 4005 (Proxy): Exception in call to czar method: Error from mysql: (-999) Error connecting to mysql with config:[host=, port=0, user=qsmaster, password=XXXXXX, db=qservCssData, socket=/home/npease/qserv-run/var/lib/mysql/mysql.sock, maxTableSize=0]
|
MariaDB [qservTest_case01_qserv]>
|
Error reporting for empty or non-consistent qservCssData should also be improved.
Running qserv-status.sh crashes.
Attachments
Issue Links
- mentioned in
-
Page Loading...
Activity
| Field | Original Value | New Value |
|---|---|---|
| Rank | Ranked higher |
| Rank | Ranked lower |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Rank | Ranked lower |
| Rank | Ranked lower |
| Rank | Ranked lower |
| Remote Link | This issue links to "Page (Confluence)" [ 20730 ] |
| Assignee | Nate Pease [ npease ] |
| Description |
Missing qservCssData db crashes Qserv when issues a sql query through czar:
The error message should be more clear and written to qserv-czar.log instead of console (console log should be thrown away in production). {code} ==> /qserv/run/var/log/qserv-czar-console.log <== terminate called after throwing an instance of 'lsst::qserv::css::CssError' what(): Error from mysql: (-999) Error connecting to mysql with config:[host=, port=0, usr=qsmaster, pass=, dbName=qservCssData, socket=/qserv/run/var/lib/mysql/mysql.sock {code} Error reporting for empty or non-consistent qservCssData should also be improved. |
Missing qservCssData db crashes Qserv when issues a sql query through czar:
The error message should be more clear and written to qserv-czar.log instead of console (console log should be thrown away in production). as of May 2019 the mysqlproxy behavior is as follows {code} MariaDB [(none)]> use qservTest_case01_qserv; Database changed MariaDB [qservTest_case01_qserv]> select objectId from Object; ERROR 4005 (Proxy): Exception in call to czar method: Error from mysql: (-999) Error connecting to mysql with config:[host=, port=0, user=qsmaster, password=XXXXXX, db=qservCssData, socket=/home/npease/qserv-run/var/lib/mysql/mysql.sock, maxTableSize=0] MariaDB [qservTest_case01_qserv]> {code} Error reporting for empty or non-consistent qservCssData should also be improved. Running {{qserv-status.sh}} crashes. |