mod.openchanfix/chanfix.cc:399 — the only statement in the DB connection check timer's handler is a commented-out call:
and checkDBConnection() itself is commented out at mod.openchanfix/chanfix.cc:3338. The timer's entire effect is therefore to re-arm itself every connectCheckFreq seconds; the database connection is never health-checked.
connectCheckFreq is not optional: chanfix.cc:269 obtains it through chanfixConfig->Require("connectCheckFreq"), so the module refuses to start without it, and mod.openchanfix/chanfix.example.conf.in:157 documents it as connectCheckFreq = 10. Operators are therefore required to configure a value that has no effect, and would reasonably believe the connection is being monitored.
Either restore the check, or remove the timer together with the config var and its example entry so the configuration stops promising something the module does not do.
mod.openchanfix/chanfix.cc:399— the only statement in the DB connection check timer's handler is a commented-out call:/*checkDBConnection();*/and
checkDBConnection()itself is commented out atmod.openchanfix/chanfix.cc:3338. The timer's entire effect is therefore to re-arm itself everyconnectCheckFreqseconds; the database connection is never health-checked.connectCheckFreqis not optional:chanfix.cc:269obtains it throughchanfixConfig->Require("connectCheckFreq"), so the module refuses to start without it, andmod.openchanfix/chanfix.example.conf.in:157documents it asconnectCheckFreq = 10. Operators are therefore required to configure a value that has no effect, and would reasonably believe the connection is being monitored.Either restore the check, or remove the timer together with the config var and its example entry so the configuration stops promising something the module does not do.