kapacitor 1.6.2 test build failure

[chenrui333]

👋 trying to upgrade the kapacitor formula to the latest release, v1.6.2, but run into some test build failure issue as below:

on the server side,

ts=2021-09-30T01:50:57.125-04:00 lvl=error msg="failed to connect to InfluxDB, retrying..." service=influxdb cluster=default err="Get \"http://localhost:8086/ping\": dial tcp 127.0.0.1:8086: connect: connection refused"

On the client side

$ kapacitor list tasks
Error: Get "http://localhost:9092/kapacitor/v1/tasks?dot-view=attributes&fields=type&fields=status&fields=executing&fields=dbrps&limit=100&offset=0&pattern=&replay-id=&script-format=formatted": dial tcp 127.0.0.1:9092: connect: connection refused

---

Just want to confirm if with the latest release, does kapacitor need influxdb for test build now? Thanks!

[docmerlin]

You shouldn't need influx for to run the tests, but yes you need influx for kapacitor if you plan on using subscriptions etc. However, the second error isn't from not having influx, but looks like maybe your firewall settings are messed up?

[chenrui333]

This is the test that we are doing kapacitor test (should not have any firewall issue?)

  test do
    (testpath/"config.toml").write shell_output("#{bin}/kapacitord config")
    inreplace testpath/"config.toml" do |s|
      s.gsub! "disable-subscriptions = false", "disable-subscriptions = true"
      s.gsub! %r{data_dir = "/.*/.kapacitor"}, "data_dir = \"#{testpath}/kapacitor\""
      s.gsub! %r{/.*/.kapacitor/replay}, "#{testpath}/kapacitor/replay"
      s.gsub! %r{/.*/.kapacitor/tasks}, "#{testpath}/kapacitor/tasks"
      s.gsub! %r{/.*/.kapacitor/kapacitor.db}, "#{testpath}/kapacitor/kapacitor.db"
    end
    begin
      pid = fork do
        exec "#{bin}/kapacitord -config #{testpath}/config.toml"
      end
      sleep 20
      shell_output("#{bin}/kapacitor list tasks")
    ensure
      Process.kill("SIGINT", pid)
      Process.wait(pid)
    end
  end

[docmerlin]

@chenrui333 Ah by test you mean you are running kapacitor straight up? If you have an influxdb specified in your config then you need an influxdb.