Skip to main content

Troubleshoot FairCom DB Notify

Use CTSTATUS.FCS to troubleshoot FairCom DB Notify

Abstract

Troubleshoot FairCom DB Notify by analyzing log messages in FairCom's log file named CTSTATUS.FCS.

Troubleshoot FairCom DB Notify by analyzing log messages in FairCom's log file named CTSTATUS.FCS, which is located in the <faircomInstallation>/data folder.

  • fcdbnotify - Not able to connect MQTT client to broker <broker>:<port>: 14305

    There is a broker connection configured at \config\dbnotifyconnections.json but DB Notify plugin was not able to connect to it. Error 14305 (Connection Error). Verify dbnotifyconnections.json and restart DB Notify plugin.

  • fcdbnotify - Couldn't find any configuration file. Please verify [\config\mqNotifications].: 14309

    DB Notify plugin is enabled but there was not any table configuration file at folder \config\dbnotify\. Valid configuration files have extension json. Error 14309 (Table publication is not found).

  • fcdbnotify - Plugin starting

    If configured at services.json, DB Notify plugin starts while FairCom DB or FairCom RTG server is starting.

  • fcdbnotify - MQTT client connected to broker  <broker>:<port>

    DB Notify plugin connected to the broker with success.

  • Stopping plugin fcdbnotify

    When serverEdge receives a shutdown instruction, it first stops the plugin. This message appears when the plugin is stopping.

  • Completed stopping plugin fcdbnotify

    This message shows that fcdbnotify plugin was stopped.

  • fcdbnotify - Plugin stopped.

    DB Notify plugin was stopped by command line (ctadmn).

  • fcdbnotify - Plugin starting.

    DB Notify plugin was started by command line (ctadmn).

  • fcdbnotify - Not able to start notification for the table list and will retry later: <error message>

    There was an error while trying to start notifications. Check <error message>. For example, there is a notification configured for table <tablename> but this table could not be found. DB Notify plugin keeps trying to open it.

  • fcdbnotify - Notification for table <tablename>  was started with success.

    If there was a table that could not be found (see previous error) then when the file is open with success, this message is logged.

  • fcdbnotify - Not able to logon to the local DBEngine - <error message>

    DB Notify plugin was not able to logon to the local DBEngine. It is necessary to solve this issue to proceed.

  • fcdbnotify - Not able to start publication for the table list: Not able to connect to the local database [<database name>] - <error message>.: <error number>

    It was not possible to connect to the local database. Verify key "databaseName" at .json files from folder \config\dbnotify\

  • fcdbnotify - Not able to stop publication for the table list: <error message>

    While stopping DB Notify plugin, all publications are stopped. Look at <error message>. Probably it is related to a previous error.

  • fcdbnotify - MQTT client disconnected from broker <broker>:<port>: 14305

    DB Notify plugin was disconnected from broker. Verify if broker is still running.

  • fcdbnotify - Not able to load list of brokers: <error message>

    It was not possible to load list of brokers at dbnotifyconnections.json. Verify <error message>. It can happen, for example, if it was not possible to open the file or if it is an invalid json file.

  • fcdbnotify - Not able to load list of tables: <error message>.

    It was not able to identify list of tables to be used with DB Notify plugin while reading files at /config/dbnotify. Check <error message> for details. It can happen, for example, if configuration folder is not found or if it is an invalid json file.

  • fcdbnotify - Not able to start publication for the table list: <error message>.

    It was not able to start publication for configured tables. Check <error message> for details. Possible problems can be: error to logon to local server, error to connect to database, error to open table exclusively.

  • MQTTTablePub::GetJsonFromRecord error - <error message>

    While preparing a message with fields value to publish, DB Notify plugin tries to read fields value. This error will be logged if there is an error to read them. Look at <error message> for more information.

  • fcdbnotify CleanUpOldcb Error: Failed to allocate callback output buffer.

    Error to allocate buffer.

  • fcdbnotify CleanUpOldcb Error: Failed to get record update callback functions: [<table name>] <error code> (<sysiocod>)

    It was not possible to get record update callback control for <table name>.

  • fcdbnotify CleanUpOldcb Error: Not able to remove record update callback [<callback name>] for table [<table name>].

    DB Notify plugin check if there are any old plugins related to DB Notify but that are not used anymore and tries to delete them. If that operation fails, this message is logged.

  • rucbOpenFileCallback - Error creating table context: <error message>

    Check <error message>. Can be due to error while trying to logon to server or while opening the table. If there are filter conditions on configuration file, a compile error can generate this message.