IPv4 Flamethrower quit abruptly on FreeBSD 12
IPv4 Flamethrower quit abruptly in stress:recursive:freebsd12:amd64 CI job over the v9_11_sub
branch:
2021-02-23:03:31:55 INFO: starting TCP generators
2021-02-23:03:31:55 INFO: starting generator #3 (tcp) on 10.53.0.3 in /var/tmp/gitlab_runner/builds/YdCaoq4b/0/isc-private/bind9/output/generator3
2021-02-23:03:31:55 INFO: (using query file /var/tmp/gitlab_runner/builds/YdCaoq4b/0/isc-private/bind9/output/query_datafile)
2021-02-23:03:31:55 INFO: starting generator #4 (tcp) on [fd92:7065:b8e:ffff::3] in /var/tmp/gitlab_runner/builds/YdCaoq4b/0/isc-private/bind9/output/generator4
2021-02-23:03:31:55 INFO: (using query file /var/tmp/gitlab_runner/builds/YdCaoq4b/0/isc-private/bind9/output/query_datafile)
2021-02-23:03:31:55 INFO: checking processes, 1 hours 0 minutes left
2021-02-23:03:32:56 INFO: checking processes, 59 minutes left
2021-02-23:03:32:56 ERROR: process with PID file /var/tmp/gitlab_runner/builds/YdCaoq4b/0/isc-private/bind9/output/generator3/generator.pid (pid = 60111) is no longer running
generator3/generator.log
does hot have the usual final summary when it exits correctly:
--class: "IN"
--dnssec: true
--help: false
--qps-flow: null
--targets: null
--version: false
-F: "inet"
-M: "GET"
-P: "tcp"
-Q: "10000"
-R: false
-T: "A"
-b: null
-c: "10"
-d: "1"
-f: "/var/tmp/gitlab_runner/builds/YdCaoq4b/0/isc-private/bind9/output/query_datafile"
-g: "file"
-l: "0"
-n: "0"
-o: null
-p: "5300"
-q: "10"
-r: "test.com"
-t: "3"
-v: "99"
GENOPTS: []
TARGET: "10.53.0.3"
file: push "091195.test.example.."
file: push "099598.test.example.."
file: push "011761.test.example.."
file: push "097867.test.example.."
file: push "025447.test.example.."
file: push "037011.test.example.."
file: push "050838.test.example.."
file: push "022788.test.example.."
file: push "093318.test.example.."
file: push "076772.test.example.."
0 key/value generator arguments
binding to 0.0.0.0
flaming target(s) [10.53.0.3] on port 5300 with 30 concurrent generators, each sending 100 queries every 1000ms on protocol tcp
query generator [file] contains 105000 record(s)
rate limit @ 10000 QPS (333.333 QPS per concurrent sender)
0.00130632s: send: 0, avg send: 0, recv: 0, avg recv: 0, min/avg/max resp: 0/nan/0ms, in flight: 0, timeouts: 0
1.01032s: send: 3000, avg send: 3000, recv: 2200, avg recv: 2200, min/avg/max resp: 39.3282/225.582/593.608ms, in flight: 822, timeouts: 0
There's no core dump file in the artifact archive.
According to logs named
instances appear to be working at the time when generator #3 quit.