← Back to team overview

linux-traipu team mailing list archive

[Bug 956223] [NEW] Unknown slave config file options crash Drizzle

 

Public bug reported:

Wrong, bad, unknown, misplaced, etc. config file options in a slave
config file cause the slave plugin to crash Drizzle at startup.

To reproduce:

1. Use a config file like:

seconds-between-reconnects=5
max-reconnects=2
[master1]
master-host=127.0.0.1
master-user=slave1
master-pass=foo
master-port=3001

(max-reconnects is misplaced).

2. Start Drizzle and observe it fold like a lawn chair:

terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::program_options::unknown_option> >'
  what():  unknown option max-reconnects
120315 11:15:35 - drizzled got signal 6;

Suggested fix: catch errors, print errors, let Drizzle start.

Workaround: fix the slave config file.

** Affects: drizzle
     Importance: Undecided
         Status: Confirmed


** Tags: crash low-hanging-fruit slave-plugin

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/956223

Title:
  Unknown slave config file options crash Drizzle

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  Confirmed

Bug description:
  Wrong, bad, unknown, misplaced, etc. config file options in a slave
  config file cause the slave plugin to crash Drizzle at startup.

  To reproduce:

  1. Use a config file like:

  seconds-between-reconnects=5
  max-reconnects=2
  [master1]
  master-host=127.0.0.1
  master-user=slave1
  master-pass=foo
  master-port=3001

  (max-reconnects is misplaced).

  2. Start Drizzle and observe it fold like a lawn chair:

  terminate called after throwing an instance of 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::program_options::unknown_option> >'
    what():  unknown option max-reconnects
  120315 11:15:35 - drizzled got signal 6;

  Suggested fix: catch errors, print errors, let Drizzle start.

  Workaround: fix the slave config file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/956223/+subscriptions


Follow ups

References