Replikwando Error Logging

Contained within this page are the inner workings of Replikwando's logging system as of version 1.7.0.

Log Levels

This setting determines what severity of issue is logged. Each level includes all the ones of higher priority as well.

Values

This value can be set in replication.ini, logging::loglevel.

Only one value is accepted, in the form of:

• loglevel=<log_level_value>

Acceptable values are (in order of criticality):

• CRITICAL
• ERROR
• WARNING
• GENERAL
• NOTIFY

Critical

Notifies the user that there are issues that require immediate attention (whether by user or programmer), and that Replikwando cannot function normally until they are corrected.

Examples:

• Basic configuration is not set
• Could not connect to local or remote database on startup
• Binary logging is not enabled
• Could not create or open sqlite file
• Processing threads have died unexpectedly (programmer must correct)
• CRT or other generic unhandled error or exception (programmer must handle)

Error

Notifies the user that issues are coming up that are stopping Replikwando from functioning correctly.

Examples:

• Loss of local or remote connection
• Inability to trigger a heartbeat

Warning

Notifies the user that some issues are coming up, but Replikwando is capable of getting along without intervention.

Examples:

• Any query that errors out for known reasons like DUPLICATE KEY or ALREADY_EXISTS

General

Details important state changes (like repushing) and other things that are nice to know, but won't require action by the users.

Examples:

• Repush started
• Repush finished

Notify

Details general state changes and higher-level debugging information.

Examples:

• Heartbeat message received
• Discarded known duplicate query (ROLLBACK; ROLLBACK;)
• Function creation without determinism set
• Short-form queries being added to sqlite file

Known Errors

Please review this wiki page.