Kapacitor: fails to start when Database not found in one database but exists on other DB

Versions: Influx 1.0, kapacitor 1.1

Start of kapacitor fails and noticed that it failed due to the database not found. We have 2 influxDB databases behind the LB. Some has created test_database on one influxDB and forgot on other InfluxDB. This makes kapacitor fails to start .

Checked the kapacitor.conf to see if the there is an option to ingore the subscription errors and brings up the kapacitord. But I didn't find one.

The request here is , there should be in some parameter in .conf file to set whether to kapacitor can ignore these subscription errors just by logging the info to the log file.

Error in log:

[run] 2016/11/17 17:43:54 I! Kapacitor starting, version 1.1.0, branch master, commit 939fdf670b028c142944977dcfcb045cac2343ed
[run] 2016/11/17 17:43:54 I! Go version go1.7.3
[srv] 2016/11/17 17:43:54 I! Kapacitor hostname: kapacitor_1aqa
[srv] 2016/11/17 17:43:54 I! ClusterID: dd2f337a-d61f-49a7-8a6f-36814b482d97 ServerID: c8de01b4-0a5c-4af3-bf25-95241b231ab2
[task_master:main] 2016/11/17 17:43:54 I! opened
[srv] 2016/11/17 17:43:55 E! error closing service *stats.Service: error closing stats service: service not open
[httpd] 2016/11/17 17:43:55 I! Closed HTTP service
[task_master:main] 2016/11/17 17:43:55 I! closed
[run] 2016/11/17 17:43:55 E! open server: open service *influxdb.Service: creating sub kapacitor-dd2f337a-d61f-49a7-8a6f-36814b482d97 for
 db "testing_emmo" and rp "default": database not found: testing_emmo

Reproduce the startup failure with the reported InfluxDB 1.0 setup, where a configured database exists on one backend but not the other. Inspect the Kapacitor configuration handling and InfluxDB service startup path; done means a configuration option can make missing subscription databases log errors without preventing Kapacitor from starting.