Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-4308

Missing qservCssData db crash Qserv

    Details

    • Type: Bug
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: Qserv
    • Labels:
      None
    • Templates:
    • 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

            Activity

              People

              • Assignee:
                npease Nate Pease
                Reporter:
                jammes Fabrice Jammes
                Watchers:
                Andy Salnikov, Fabrice Jammes, Fritz Mueller, Jacek Becla, John Gates, Nate Pease
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:

                  Summary Panel